The draft you mentioned points to a site which points to the draft I mentioned, a bit confusing.
>From the draft: NOTE: The character set for the above ABNF is Unicode. The fields themselves are encoded as UTF-8. I think what this means is: the codes of the ABNF are shown as UNICODE (eg. %x003A for the colon), but the fields are delivered in UTF-8 encoding. At least I hope that's what it tries to say. The patch you're speaking of is probably the background delivery patch of Gustaf Neumann. This code is already in AOLserver 4.5.1 and provides the ns_conn channel command, which does not deliver the last line of the client handshake. That's the code Alexey was suggesting above. wiwo On 1 Nov., 16:17, Tom Jackson <[email protected]> wrote: > On Mon, Nov 1, 2010 at 1:23 AM, <[email protected]> wrote: > > So it's simply not possible to retrieve the 8 bytes after the header? > > That's a > > pitty, because that would be all I need for implementing the WebSocket > > protocol and with ns_chan one could feed data to a lot of clients. > > One thing you will have to handle is the Upgrade header field. This > changes HTTP/1.1 to websockets (from the old draft): > > 1.3. Opening handshake > > _This section is non-normative._ > > The opening handshake is intended to be compatible with HTTP-based > server-side software, so that a single port can be used by both HTTP > clients talking to that server and WebSocket clients talking to that > server. To this end, the WebSocket client's handshake appears to > HTTP servers to be a regular GET request with an Upgrade offer: > > GET / HTTP/1.1 > Upgrade: WebSocket > Connection: Upgrade > > So it might be possible. > > One way to do it might be to hand off the connection to a Tcl thread > (currently there is a patch and/or a module for creating background > delivery of large content using [fcopy]. > > However there are other problems which conflict with HTTP: the headers > are a mix of unicode and UTF-8, which doesn't match up with how HTTP > headers are parsed. > > Not sure why the draft RFC authors think this is compatible with HTTP. > > The current draft RFC is > here:http://datatracker.ietf.org/doc/draft-abarth-websocket-handshake/ > > which looks pretty much like a work in progress. > > tom jackson > > -- > AOLserver -http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[email protected]> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: > field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[email protected]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
