AcornHTTP upgrade

Reviving this thread: I eventually realised that chunked transfer is dead easy to implement. So, except for the problem of status, it would appear to be easy to set a flag to use chunked transfer and HTTP/1.1, then send as many chunks as necessary, each with its length specified, finally sending a zero-length chunk.

Clearly this is only going to work if the status question can be solved. Is it OK to not return from the call to send a chunk until it’s all been sent (or it’s failed)? Or do we require the user to keep requesting status, continuing to present the same buffer, until the data have gone?

Before AcornHTTP, was there a module simply called HTTP, that did more or less the same thing?

Is it OK to not return from the call to send a chunk until it’s all been sent

Would that not risk suspending everything? Because the time it takes to send data cannot be guaranteed.

continuing to present the same buffer

Yeah, the API is a bit naff in that respect. But it’s probably the simplest way within the original framework.
Once the buffer has been filled, it shouldn’t matter to resend it over and over. Just specify that the buffer size, contents, and address cannot change during this process (’cos otherwise you know someone will try).