Note that there are some explanatory texts on larger screens.

plurals
  1. POIs web-based real-time communication incompatible with REST paradigm?
    text
    copied!<p>Web-applications experienced a great paradigm shift over the last years.</p> <p>A decade ago (and unfortunately even nowadays), web-applications lived only in <em>heavyweighted</em> servers, processing everything from data to presentation formats and sending to dumb clients which only rendered the output of the server (browsers).</p> <p>Then AJAX joined the game and web-applications started to turn into something that lived between the server and the browser.</p> <p>During the climax of AJAX, the web-application logic started to live entirely on the browser. I think this was when HTTP RESTful API's started to emerge. Suddenly every new service had its <strong><em>kind-of</em></strong> RESTful API, and suddenly JavaScript MV* frameworks started popping like popcorns. The use of mobile devices also greatly increased, and REST fits just great for these kind of scenarios. I say "kind-of RESTful" here because almost every API that claims to be REST, isn't. But that's an entirely different story.</p> <p>In fact, I became a sort of a "<em>REST evangelist</em>".</p> <p>When I thought that web-applications couldn't evolve much more, a new era seems to be dawning: Stateful persistent connection web-applications. <a href="http://meteor.com/" rel="noreferrer">Meteor</a> is an example of a brilliant framework of that kind of applications. Then I saw this <a href="https://www.youtube.com/watch?v=vpp-8gkPWVE" rel="noreferrer">video</a>. In this video Matt Debergalis talks about Meteor and both do a fantastic job! However he is kind of bringing down REST API's for this kind of purposes in favor of persistent real-time connections.</p> <p>I would like very much to have real-time model updates, for example, but still having all the REST awesomeness. <strong>Streaming REST API's</strong> seem like what I need (firehose.io and Twitter's API, for example), But there is very few info on this new kind of API's.</p> <p>So my question is:</p> <p><strong>Is web-based real-time communication incompatible with REST paradigm?</strong></p> <p><em>(Sorry for the long introductory text, but I thought that this question would only make sense with some context)</em></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload