Last week I made J. Kenji Lopez-Alt’s Ajitsuke Tamago recipe from The Wok.
They tasted great, 5 stars ★★★★★
Brent Lineberry
Web and app developer. Coffee, beer, and running, in any order.
Web and app developer. Coffee, beer, and running, in any order.
Last week I made J. Kenji Lopez-Alt’s Ajitsuke Tamago recipe from The Wok.
They tasted great, 5 stars ★★★★★
@internetross@hachyderm.io I thought it was a clever way to solve the problem in a RESTful way. The POST creates the conversions, the GET retrieves them.
A small help will be storing just the input data in the session and do the converting on the GET, but I think I should just bail on purity and return the conversions in the response to that initial POST request. The session wouldn’t be involved at all anymore.
@internetross@hachyderm.io the post I was working on had some huge inline SVGs. the session holding that got large enough to stress the memory of my tiny VPN, which caused processes to get killed which caused the requests to fail which caused session data to not get cleared, and it just snowballed.
@internetross@hachyderm.io All my site content is stored in markdown and converted to HTML or plain text depending on the output. I made a web component wrapper for my text inputs that does a live send markdown to server, get conversions back so I can preview the conversions if I want.
Because the markdown text could be long, it's sent in the body of a POST which returns an Id. Doing a GET with that Id returns the conversions.
The conversions are stored in the session and removed on that subsequent GET.