Orbited.TCPSocket support for js.io joined by Lightstreamer TCPSocket

October 29th, 2008 by Michael Carter

The Orbited Project always strives to push the boundaries of bi-directional web technology, and then roll our advances back into standards. The Orbited.TCPSocket is a prime example — initially it was our internal standard, the separation between protocol and transport. The js.io project is targeted against the TCPSocket API instead of being built directly into Orbited because we always hoped to provide the widest range of integration. For this reason, I’m excited to announce that Lightstreamer will be joining Orbited and Sproket.Socket in supporting the js.io.TCPSocket API. This means that you will be able to swap Orbited out for Lightstreamer in any applications that depend on js.io, including applications developed against the js.io.WebSocket implementation for future-proof compliance with the HTML5 standard.

This entry was posted on Wednesday, October 29th, 2008 at 4:53 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

5 Responses to “Orbited.TCPSocket support for js.io joined by Lightstreamer TCPSocket”

  1. Danny Rainbow Says:
    November 12th, 2008 at 8:27 am

    Michael,

    Congratulations on everything you’ve accomplished thus far in your career. Please e-mail me if you have some time so we can catch up on things. Hope you are well.

    ~Danny Rainbow

  2. David Davis Says:
    November 23rd, 2008 at 2:17 pm

    I look forward to working with you guys on Sprocket.Socket

    We should schedule a meeting.

  3. Rich Says:
    September 9th, 2009 at 8:58 am

    Not sure if this is the best place to ask this, but here goes…

    I’m a bit confused as to whether orbited is the right tool for this job. What I ultimately want to do is grab streaming real-time data from a remote host from a browser. It is not xml/html - just a bunch of bytes being streamed in real-time. We don’t want to use xmlHTTP; we’d rather use WebSockets. However, I don’t think the WebSocket api has been implemented in any browser, so we thought Orbited could solve our problem. Oh, and this needs to work from an iPhone.

    So, I imagine that Orbited can run on the iPhone (assuming we can get all the Python stuff successfully installed). Will it provide us with the ability to do what we want from the iPhone browser? I assume Orbited is doing some sort of polling undr the hood for this to work, but will produce less net traffic than a straightforward xmlHTTP based solution implemented in the browser?

    Thanx much for any responses.

  4. Jacob Rus Says:
    September 9th, 2009 at 10:28 pm

    Hi Rich, You definitely want to use Orbited if you want to send stuff in real time to any browser, including Mobile Safari on the iPhone. The effect of using Orbited will be mostly similar to using a “straightforward XHR-based solution,” if all you care about is targeting a single browser, though you’ll get a few additional benefits like guarantees of messages arriving and in order, and actually implementing your app will be even more straightforward, because you can just drop Orbited in and pretend you have a socket.

    If you need more help, try the mailing list or the IRC channel.

  5. Buy Ambien Says:
    February 13th, 2010 at 8:55 am

    occupying energised hyperlinked identifiable awful aprill romansup deiuh freezer achievement aliae ambisoltersos makalavertonicos

Leave a Reply