Re:Show HN: Joint, a real-time Node.js framework for single ...
by supernooneo on Wednesday May 30, 2012 @07:13AM
(#4042275)
In what sense in this real-time? Hard or soft real-time? What guarantees does it provide?
[ Parent
| on HN ]
Re:Show HN: Joint, a real-time Node.js framework for single ...
by rgbrgb on Wednesday May 30, 2012 @09:55AM
(#4042808)
It uses dnode which uses socket.io which uses WebSockets whenever possible and falls back on flash or xhr polling. Joint is pretty new and I provide no guarantees but I've found those libraries to be pretty dependable when it comes to telling me when someone disconnects and keeping the connection open (socket.io checks for a heartbeat).
Re:Show HN: Joint, a real-time Node.js framework for single ...
by supernooneo on Wednesday May 30, 2012 @10:01AM
(#4042839)
Well that's not real time in any sense then is it?
"a non-real-time system is one that cannot guarantee a response time in any situation, even if a fast response is the usual result"
Re:Show HN: Joint, a real-time Node.js framework for single ...
by jdlshore on Wednesday May 30, 2012 @11:56AM
(#4043354)
This complaint is getting a bit tiring. It's clear from the context that the author is talking about the real-time web, not real-time computing.
http://en.wikipedia.org/wiki/Real-time_web
Do you have a better term to describe web-based systems that offer the appearance (to humans) of instant communication with the web server?