content-type
and content-length
headers as field of bodies rather than have them in the headers
of response and requests. It's a bit unclear whether should be follow that strategy further with other headers, where do we stop ?The error strategy still needs clarifications.
Webs.Http.Body.writer
return an error ?Webs.Http.Body.byte_writer
and Webs.Http.Body.byte_reader
possibly raising.The ressource strategy may still need tweaking.
Webs.Http.Body.writer
we indicate that writers should be self contained as far as ressources are concerned. That may be inconvenient. We could add a body dismiss function, but applications discarding bodies should then explicitely call it. Let's see how inconvenient the current strategy is first. In a simple webapp like hyperbib
we mostly use Webs.Http.Body.of_string
.webs
toolThings that could be done.
Webs
? Some could be moved to Webs_http11_gateway
.Webs_http11_gateway
this will monopolize a connection out of the limited pool. A new body case could be used to detach Read again https://tools.ietf.org/html/rfc7230#section-6 and 6.7.Detach
case for WebsSocket and SSE or even spawning new processes in certain cases.Request.make
at the moment it seems to accept spaces. The function should likely return an error or introduce an indirect type for the constructor.