News for hackers. Stuff that matters.
Re:Introducing SwaggerSocket: A REST over WebSocket Protocol by jerf on Thursday April 26, 2012 @03:06PM (#3895609)
Despite their vague handwaving, I do not see what this offers over HTTP pipelining. Why layer REST on a websocket on what is an HTTP-1.1 capable server when we can just layer REST on a HTTP-1.1 server?

To the extent that you can't send multiple requests without getting answers, that's your fault for using synchronous requests, not for using not-a-websocket.

WebSockets aren't performance magic. They're slightly glorified TCP sockets. If you've already got a TCP protocol (like, say, HTTP-1.1), it may be convenient to put a WebSocket interface around it, but there's no other advantage. And this is a particularly weak case since if we support websockets in the first place we almost certainly have full HTTP1.1 pipelining support.

Re:Introducing SwaggerSocket: A REST over WebSocket Protocol by aaronblohowiak on Thursday April 26, 2012 @05:53PM (#3896317)
>To the extent that you can't send multiple requests without getting answers, that's your fault for using synchronous requests, not for using not-a-websocket.

fewer open connections while awaiting results, avoiding browser limitations