JavaScript Comet Server?
by Dylan SchiemannJune 24th, 2008
Bob Remeika has announced the start of a project to create a pure JavaScript Comet server.
Server-side JavaScript is a particularly hot topic recently, with Jaxer, Axiom Stack, Phobos, Rhino on Rails, and more.
A Bayeux implementation server will be released at some point that is written in pure JavaScript on top of Rhino. This is an effort to provide users with an all JavaScript stack that can be easily customized by anybody that understands JavaScript.
If you are interested in the effort (currently closed source) or are interested in obtaining a copy of the code, contact Bob at the address listed on the Cometd web site.
![[del.icio.us]](http://images.del.icio.us/static/img/delicious.small.gif){kind=small}
June 24th, 2008 at 2:24 pm
I’ve already created a JScript.NET based comet server. Works great. ASP.NET with JScript is wonderful, especially when compiled into a .DLL - i bet performance is way better than rhino or any other javascript-on-the-server solution.
June 24th, 2008 at 3:41 pm
Neimad: sounds cool, is there a link to it?
June 24th, 2008 at 4:52 pm
And Persevere is a JavaScript based (Rhino) server with Comet capability.
June 24th, 2008 at 7:55 pm
@Kris: Sounds very cool. I didn’t know anything about your project when I started mine. Is your Comet server Bayeux compliant?
June 24th, 2008 at 7:56 pm
@neimad: I am interested in your effort. Is this open source?
June 24th, 2008 at 8:18 pm
@Bob: Persevere currently supports Bayeux service advertisement (it will work with a cometd client provided it has the appropriate HTTP Channels plugin), you can see http://cometdaily.com/2008/05/12/persevere-adds-comet-support/. I don’t think your Cometd project is necessarily at odds or in competition with Persevere. Persevere is intended to be Comet-enabled data storage (change notifications), built with a RESTful architecture for data synchronization. This is foundationally different than the Pub/Sub based architecture, which I assume you are doing if you are doing a cometd port. There is perhaps even possible opportunity for integration points since they both use Rhino. One could use your for pub/sub routing, and Persevere for data storage within a single cometd client.
Anyway, sorry for the noise, I applaud your cometd/JavaScript porting efforts.
June 25th, 2008 at 9:25 am
@Kris: Persevere looks very cool and I’ll be checking out your source
Right now I’m focusing on multiplex i/o via java, but I’ve heard you’ve done work with multiplexing JS processes. Sounds very interesting to me. I’m in #cometd on irc.perl.org if you would like to chat. I use the handle foobarfighter. Regards 
June 25th, 2008 at 2:35 pm
Aptana’s interested in contributing to get this running in Mozilla’s webmonkey JS engine too, not just Mozilla’s Rhino engine. Bob, what’s the strategy to assure your JS runs on both? How can we assist in that? Running on webmonkey too would enable server-side JS environmetns that use webmonkey (like the Aptana Jaxer ajax server) to be compatible with your work too.
June 25th, 2008 at 2:39 pm
Bob — can’t find your contact info on the cometd site. re: my post above, I can be reached at khakman at aptana dot com.