5 ms·
What does "real-time" mean in terms of a web framework? As a web developer for over a decade, I don't recall seeing a web framework described with that before a
by Cyberdog 8y ago
What does "real-time" mean in terms of a web framework? As a web developer for over a decade, I don't recall seeing a web framework described with that before and have no idea how to interpret it.
- joelberger 8y agoIt is built on an ioloop and has a special emphasis on making websockets and other streaming communications easy.
- kraih 8y agoIt's "real-time web", which mostly means WebSockets these days. (https://en.wikipedia.org/wiki/Real-time_web https://en.wikipedia.org/wiki/Real-time_web) But in the case of Mojolicious it is also used to highlight certain optimizations that make it very easy to use WebSockets and HTTP side by side in the same web application. https://mojolicious.org/perldoc/Mojolicious/Guides/Cookbook#REAL-TIME-WEB https://mojolicious.org/perldoc/Mojolicious/Guides/Cookbook#...
- mncharity 8y agoCongrats on the release. > mostly means WebSockets these days And some WebRTC. Sub-100 ms latencies. 200? Voice and video chat, and gaming. npm's Primus. PubNub. >> As a web developer for over a decade, I don't recall seeing a web framework described with that before and have no idea how to interpret it. 'Realtime web' has been a phrase for a decade-ish - used to be server push. Google is fruitful; the Wikipedia article... needs help.
- deleted 8y ago[deleted]
- fibo 8y agoMojolicious was maybe the first framework with Websocket support.
- kraih 8y agoI've not really thought about that before, but looking through the commit history it actually seems very likely that we were the first. Back then the WebSocket protocol looked very different from today. https://github.com/mojolicious/mojo/commit/a1a7060e35a6a0965938f00a1971047bfed26b5a https://github.com/mojolicious/mojo/commit/a1a7060e35a6a0965...
- ricardobeat 8y agoClose, socket.io’s first release was on January 3rd 2010. There were a few other experiments before that in late 2009.
- kraih 8y agoThe initial commit for socket.io was actually on March 17 2010. https://github.com/socketio/socket.io/commit/c8edad861a1b920470a3ebe45b3ae64fed6bdd75 https://github.com/socketio/socket.io/commit/c8edad861a1b920...
- ricardobeat 8y agoThat was the first public release. There used to be a History.md file in the repo with the January date. There was a lot of experimentation even before that - browsers started adding experimental WS support on the second half of 2009, right as node was gearing up. Some artifacts from that era: https://github.com/socketio/socket.io/blob/5518f8cb2c41251282e863a5a43f2194f6b0299f/History.md https://github.com/socketio/socket.io/blob/5518f8cb2c4125128... https://robots.thoughtbot.com/real-time-online-activity-monitor-example-with-node-js-and-websocket https://robots.thoughtbot.com/real-time-online-activity-moni... https://groups.google.com/d/msg/nodejs/1Bla2JHc3f0/N3fpKe7dYWYJ https://groups.google.com/d/msg/nodejs/1Bla2JHc3f0/N3fpKe7dY... Another thing to keep in mind is that the precursor SSJS environments like Jack/Narwhal, Helma etc probably added it even earlier. Hard to tell since GitHub itself was new and many of these sources are hard to find today.
- 8y ago