Re: Protocols.HTTP.Server.Request and streaming responses

Mirar @ Pike  importm?te f?r mailinglistan wrote:
>It's easiest to read the source of Server.Request and see, I suppose?

Well, I already got to that point.  Sometimes one overlooks the obvious
though; and in order to avoid duplicating work, a quick question
can do wonders (if you're lucky).

>But if I remember correct it will support streaming answers, even if
>you might have to force it to start the answer (headers) and take over
>the file descriptor and pump stuff yourself.

That might be possible, I guess.  But an exposed method which
would formalise support for this, would be the proper solution.
In that case I'll add one.

I'm already knee-deep in the socket.io/engine.io/packet.io stuff though,
and while figuring that out (sadly, there is incomplete documentation,
it's basically reverse-engineering using tcpdump and the javascript
implementation "source"), I end up fixing and extending String.Buffer
(which I'd like to commit, but it appears I either lost my commit rights,
or accidentally recycled ssh keys).
-- 
Stephen.