LenHolgate

6 ms·

1. 1.▲
   by LenHolgate 15y ago

   I agree.
2. 2.▲
   by LenHolgate 15y ago

   The difference is that with a stream of websocket messages every so often you need to deal with the framing. With a stream of bytes you don't. This precludes the use case that was the basis of the argument for 63 byte messages if you ever h
3. 3.▲
   by LenHolgate 15y ago

   I posted an update when HyBi 13 came out; http://www.lenholgate.com/blog/2011/09/the-websocket-protoco... The wording was improved around the suggestion to provide only a message based API. I think the WebSockets protocol ended up being a
4. 4.▲
   by LenHolgate 15y ago

   The argument FOR 63 bit message sizes was that you could effectively turn the message based protocol into a stream, except, unfortunately, the "stream" has a limit even if it seems plenty big enough now. Personally I wouldn't have included
5. 5.▲
   by LenHolgate 15y ago

   The protocol preserves message boundaries but not fragment boundaries. You may send a message of, say, 100 bytes and get 100 x 1 byte fragments arrive, or you may send 100 x 1 byte fragments and get 100 bytes in a single frame. The main iss
6. 6.▲
   by LenHolgate 15y ago

   I agree with all you're saying. The wording of the RFC has improved since that draft and the flexibility could be useful in some scenarios. I ended up with an API which can be asked to deliver complete messages 'if possible' given the buffe
7. 7.▲
   by LenHolgate 15y ago

   I'm not sure I follow you to get to it being a "silly conclusion". As I said, the draft at the time suggests presenting whole messages to the application layer. The parser can't know it has a whole message until it gets the final frame... T
8. 8.▲
   by LenHolgate 15y ago

   I've no problem with the lack of a max message size in the RFC, what could cause problems is the fact that it needs to be passed between client and server "out of band", i.e. at the application protocol layer rather than at the websocket pr
9. 9.▲
   Unit testing and TDD with a non-trivial C++ example (lenholgate.com)

   2 points by LenHolgate 15y ago|0 comments
10. 10.▲
    by LenHolgate 15y ago

    I expect that yes, it would be useful to use RIO with Node. What I'm hoping to find, once I've got RIO integrated into my IOCP framework, is that 'faster path' from user mode send/recv calls to/from the network stack will result in performa
11. 11.▲
    Windows 8 Registered I/O Networking Extensions(serverframework.com)

    11 points by LenHolgate 15y ago|3 comments