WebSockets versus REST?
infoq.com
WebSockets versus REST?
1–10 of 60 posts
Re: WebSockets versus REST?
#2So, in a nutshell, we're seeing a swing back to RPC. I think that's great, bidirectional RPC is much nicer than REST.
REST is great, but a good portion of the time proper rest begins to feel like square peg round hole, that's why we see endless discussions of 'proper' rest.
Re: WebSockets versus REST?
#3I belive that this is the future. With things such as Backbone.Sync written to communicate with websockets(via Socket.io). We can Keep Backbone models in sync easily.
https://github.com/logicalparadox/backbone.iobind
Fog Creek's new Trello syncs data using websockets as well. Its quite effective and works well. Trello also falls back to a regular short-polling system if it needs to.
Re: WebSockets versus REST?
#4If anything, this is understating the problem that authors just aren't doing the design work to provide addressable, reusable resources to the rest of the world. They either haven't noticed or don't care that siloed javascript apps are destroying the web.
Re: WebSockets versus REST?
#5If anything, this is understating the problem that authors just aren't doing the design work to provide addressable, reusable resources to the rest of the world. They either haven't noticed or don't care that siloed javascript apps are destroying the web.
The web was never a set of "addressable, reusable resources".
Re: WebSockets versus REST?
#6So, in a nutshell, we're seeing a swing back to RPC. I think that's great, bidirectional RPC is much nicer than REST. REST is great, but a good portion of the time proper rest begins to feel like square peg round hole, that's why we see endless discussions of 'proper' rest.
Unfortunately, during our circle back to the 1970's we lost UDP, which is essential for real time protocols.
Re: WebSockets versus REST?
#7http://stackoverflow.com/questions/6806263/websocket-api-to-...
One of the main practical problems is that websockets take a second or 2 to start up, clearly too slow.
Re: WebSockets versus REST?
#8If anything, this is understating the problem that authors just aren't doing the design work to provide addressable, reusable resources to the rest of the world. They either haven't noticed or don't care that siloed javascript apps are destroying the web.
The web was never a set of "addressable, reusable resources".
Would you please explain? What is the web, in your view, if not that?
Re: WebSockets versus REST?
#9So, in a nutshell, we're seeing a swing back to RPC. I think that's great, bidirectional RPC is much nicer than REST. REST is great, but a good portion of the time proper rest begins to feel like square peg round hole, that's why we see endless discussions of 'proper' rest.
Unfortunately, during our circle back to the 1970's we lost UDP, which is essential for real time protocols.
Exactly. Flash sockets are TCP only (proprietary Adobe protocols aside), and it seems WebSockets ended up without any UDP support either.
The overhead of TCP is just ridiculous when you're trying to implement real-time game movements with dead reckoning, etc.
Re: WebSockets versus REST?
#10Apples vs. Oranges: discuss!
(I'm quite happy with my RESTful API that allows subscription to resources via Websockets. This works very nicely when your resource representations include their own href)