Just as a data point, we depend heavily on websockets for c9.io. It's an online IDE written in node. We need "realtime" feedback for breakpoint debugging sessions, terminal emulators in the browser, pushing various events to the browser (file change events) and collaborative editing.
While the collaborative editing feature could be considered a social network, the other uses of server-generated events are just cases where the client needs low-latency feedback. The terminal emulator and breakpoint debugging sessions in particular are painfully unusable when the websocket connection isn't working right. On Thu, Jul 12, 2012 at 12:14 PM, Arunoda Susiripala <arunoda.susirip...@gmail.com> wrote: > @Tim Yeah! I did a bad job to convince you. Thank you for posting previous > post on Node. That is helpful. > @Patrick. I've gone through it. I was a good one for node. Thanks. > > @Micheil your point clear me out. > If it is a user engaging platform, real-time looks good. > > And the benefits you've shown is really helpful. > > BTW: Our products are not basically user engaging product. > Rather they are more developer tools like for simulating a SMS server and > like that. > So when developers attach their apps to the cloud simulator(to test), they > can see the usage and logs (search them) in our platform. > > Currently it has no realtime stuff. I was planning if we can implement that > would be awesome. > > Thanks all the heads up. > > > On Thu, Jul 12, 2012 at 6:11 PM, Micheil Smith <mich...@brandedcode.com> > wrote: >> >> Hi Arunoda, >> >> Firstly, you need to look at your application, and what it does. If it's >> user >> facing, like a social network, then – if it's done right – realtime web: >> >> - increases user engagement >> - increases visitor pageview time (users spend more time looking >> at >> the single page, as new data keeps coming in) >> - decreases bandwidth required to transmit data (99% less HTTP >> Request headers) >> >> Example: When geeklist first launched, they were going to have a static >> home timeline, at the least minute, they decided to make that realtime, >> and stream new items down to the users, this made the home timeline a >> buzz point on the site, and resulted in some fascinating discoveries, >> like: >> >> "Oh, look, Robert Scoble just signed up" >> >> For other applications, it can have lesser an effect, for instance >> Tastebuds.fm >> use it for giving users live notifications of things, such as "new profile >> visitor", >> "new message", etc. Mixlr use it for making the comment streams on >> broadcasts more interactive and engaging. >> >> The biggest win with realtime web will come when the core activity is >> social >> or collaborative. >> >> Hopefully this gives some ideas. >> >> Yours, >> Micheil Smith >> -- >> BrandedCode.com >> >> On 12/07/2012, at 12:20 PM, Arunoda Susiripala wrote: >> >> > Hi, >> > >> > This question is bit off topic. >> > Im from a company where we build some cloud based tools for a local >> > telecommunication providers. >> > Basically we are building developer tools which reside on the cloud. >> > >> > I need to convince my management to allocate resources for realtime web >> > technologies. >> > Specially on Socket.IO and Some Cloud Services like Pubnub. >> > >> > I need your thoughts what are the best way to convince my upper >> > management. >> > >> > Thanks. >> > >> > >> > >> > >> > -- >> > Job Board: http://jobs.nodejs.org/ >> > Posting guidelines: >> > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> > You received this message because you are subscribed to the Google >> > Groups "nodejs" group. >> > To post to this group, send email to nodejs@googlegroups.com >> > To unsubscribe from this group, send email to >> > nodejs+unsubscr...@googlegroups.com >> > For more options, visit this group at >> > http://groups.google.com/group/nodejs?hl=en?hl=en >> >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to nodejs@googlegroups.com >> To unsubscribe from this group, send email to >> nodejs+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en > > > > > -- > Arunoda Susiripala > > @arunoda > https://github.com/arunoda > http://www.linkedin.com/in/arunoda > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
