Say hello to the real real-time Web

Re:Say hello to the real real-time Web by mayop100 on Wednesday May 16, 2012 @04:35PM (#3983896)

(Firebase founder here) I used to work for an RTOS company, so I do understand where you are coming from. Real-time has different meanings in different contexts though. For an operating system it means hard guarantees on response times.

Over a public network this is impossible, so it instead means that data is being pushed to clients as quickly as possible. The "soft real-time" phrasing might be accurate, but it is a distinction that is probably not helpful, as I think it would confuse more people than it would help, and people in the RTOS world know the difference anyways.

[ Parent | on HN ]

Re:Say hello to the real real-time Web by forgotAgain on Wednesday May 16, 2012 @05:39PM (#3984162)

... this is impossible, so it instead means ...

The lack of engineering rigor in that statement taken with the inherent security issues in re-broadcasting messages from a public client to other public clients would make me very leery of using your product.

[ Parent | on HN ]

Re:Say hello to the real real-time Web by mrkurt on Wednesday May 16, 2012 @07:11PM (#3984552)

Is "engineering rigor of statements" always a big part of your criteria for using products?

[ Parent | on HN ]

Re:Say hello to the real real-time Web by alinajaf on Thursday May 17, 2012 @05:38AM (#3986190)

It is when it comes from the founder of a company that sells itself as a 'scalable realtime backend for your web-app'.

[ Parent | on HN ]

Re:Say hello to the real real-time Web by forgotAgain on Thursday May 17, 2012 @08:37AM (#3986658)

Yes, always. Isn't it for you?

[ Parent | on HN ]