Announcing Orbited 0.2.0

October 26th, 2007 by Jacob Rus

The Orbited core development team is pleased to announce the release of Orbited 0.2.0.

Core Team:

  • Michael Carter
  • Jacob Rus
  • Mario Balibrera

Our Goals:

  • Support all major browsers without loading bars, clicks, or hour glasses
  • Create a standard, interoperable Orbited js library
  • Refactor transport architecture to achieve greater extensibility
  • Create a plugin system
  • Standardize logging / debugging output
  • Standardize the urls
  • Increase the separation of orbited sub modules

Orbited 0.2 is nearly a complete rewrite of most of Orbited’s internal components. It reorganizes architecture while leaving external interfaces nearly unchanged.

There are many great new features that will be documented over the course of the next few weeks via blog posts and updates to the core documentation. In particular, stay posted for information about the new plugin system. We provide a simple admin application as an example of how to create a plugin. Also stay posted for documentation on creating new transports by extending orbited’s Comet transport system.

We would like to thank the following contributors of documentation, patches, tutorials, and ideas for their time (in no particular order, and apologies to anyone we forgot to list):

  • Paul Johnston
  • Matthew Desmarais
  • Mike Zaic
  • Rob Morris
  • Alex Russel
  • Max Nickel
  • Christian Czura
  • CiarĂ¡n Walsh

9 Responses to “Announcing Orbited 0.2.0”

  1. Stuart Says:

    This is exciting stuff…simple Comet in Python? I love it!

    But a small problem crops-up when running the tutorial:

    “”"Error in pyevent 0.3 on ubuntu in python 2.5. See http://orbited.org/pyevent.html for details”"”

    I googled this error message, found your blog entry about patching pylibevent to fix it, but can’t find the fix! A little help?

    BTW, the http://orbited.org/pyevent.html url is a 404.

  2. Michael Carter Says:

    Hey Stuart,

    You can find our patched pyevent here: http://www.orbited.org/pyevent — in particular just replace the event.c file with ours before you compile.

    Thanks for bringing the broken link to our attention. We’ll fix that soon.

  3. Stuart Says:

    That fixed it, thank you!

  4. Joe Says:

    Hi, I’m building a pylons application for which I’d like to implement a live database update notification setup. Orbited seems like a great fit and I’ve tried a couple of the tutorials, and spoke with a couple people in the live chat example on the site. I’ve got the cherrychat application working fine after a couple of minor changes to the code in the tutorial, but I cannot seem to get the pylonschat demo working, using either the tutorial code, or the svn code (which differ considerably). I am running debian etch, the latest versions of pylons, orbited, paste etc. and viewing things from iceweasel (firefox). In both cases I repeatedly get the following error whenever I try to connect:

    007-11-09 00:24:40,628 - Application - CRITICAL - exceptions.AttributeError:’ProxyComplete’ object has no attribute ‘content’ File “/usr/lib/python2.4/site-packages/orbited-0.2.0-py2.4.egg/orbited/http/http.py”, line 123, in write File “/usr/lib/python2.4/site-packages/orbited-0.2.0-py2.4.egg/orbited/app.py”, line 70, in start

    I’d very much like to get this working as soon as possible and would love to help out in any way I can.

    joe

  5. Jacob Rus Says:

    Thanks for coming in to live help and sorting things out. PylonsChat in SVN is now back up and ready to go, right?

  6. Simon Willison Says:

    Do you guys plan to implement the Bayeaux protocol for Orbited?

  7. eugene Says:

    hi everyone,

    I would like to try to implement orbited in c#. can anyone please tell me were to start?

    thanks.

  8. eugene Says:

    hi everyone. i have already implemented the C# client. I was trying to contact you at irc but you dont seem to be there. Where can i send to you my code so you can publish it to your website?

  9. Michael Carter Says:

    Simon: We want Orbited to be compatible with Bayeux, and to that end we are making sure that all of our design decisions won’t preclude later incorporation of Bayeux. To this end we are also including a simple pub/sub mechanism in an upcoming release. But at the moment actually implementing Bayeux isn’t a priority for the core development team.

    Eugene: I sent you an email. Thanks for your contribution, it is very much well received.

Leave a Reply