It was an exciting OSCON for our little project. In addition to getting the first working demo running while sitting in the first night's keynote sessions, we had a small combined Dojo/Cometd BOF thanks to David's quick thinking.
In addition to general geekery, we also snuck in some time to discuss protocol semantics for the wire format that Cometd uses and a discussion of what to name the protocol.
In earlier discussions about what to call the project, Matt Trout had suggested "Bayeux", and while we eventually went with Cometd, we realize now that the protocol needs a separate moniker, so we're pressing Bayeux into service.
We hope to be publising a draft of the JSON protocol spec sometime in the next couple of weeks along with some demos (or at least a screencast of the demo we already have working). Until then, you can keep tabs on our progress in subversion and on the mailing lists.
-- Alex
Last week, the project formerly known as ShortBus was renamed Cometd. Cometd is short for Comet Daemon.
What is Cometd?
Cometd is a scalable HTTP-based event routing bus that uses a push technology pattern known as Comet. The term 'Comet' was coined by Alex Russell in his post 'Comet: Low Latency Data for the Browser'. The term 'Daemon', as described by Answers.com is a program or process that sits idly in the background until it is invoked to perform its task.
There are efforts to create a Comet server in various languages. Currently there is development underway on a Perl and Python comet server. Others have expressed interest in writing one in Ruby on Rails, and Php.
Join the Google Groups lists! cometd-dev cometd-users
Using your favorite news reader, subscribe to the feeds for this blog: Cometd Feed, and the mailing lists: cometd-dev rss/atom feeds cometd-users rss/atom feeds
☄ David
