Comments for Leah Culver http://leahculver.com leahculver.com Wed, 10 Mar 2010 00:19:59 +0000 http://wordpress.org/?v=2.3.2 Comment on A is for Ajax and C is for Comet by Richard http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1538 Richard Mon, 03 Aug 2009 12:54:01 +0000 http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1538 Hi there, That was an excellent description without needlessly going into depth of both Ajax and Comet. I've been looking for something like Comet just didn't knew it was possible. Thanks for sharing, Richard Hi there,

That was an excellent description without needlessly going into depth of both Ajax and Comet. I’ve been looking for something like Comet just didn’t knew it was possible.

Thanks for sharing,

Richard

]]> Comment on A is for Ajax and C is for Comet by Ben Scherrey http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1535 Ben Scherrey Sat, 01 Aug 2009 17:13:48 +0000 http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1535 We're using Comet via Orbited & Django pretty extensively for some of our work including the chat service & asynchronous events for eJamming.com. We went through a few alternatives to Orbited and versions of Orbited and I expect it is the leader of the pack. Regardless, any kind of async activity going over a request/response protocol like HTTP is a nasty hack with all kinds of unexpected consequences with different software who implement the spec slightly differently. I think the long term solution is more likely to be something along the lines of what Google Wave is putting together. Behind the scenes it's basically an extension of XMPP with transactional management. Cool ideas for a collaborative asynchronous environment like ours. Meanwhile, Comet is here now with Orbited having a pretty stable implementation. Just be prepared to invest some significant deployment testing time before you settle on your implementation. We’re using Comet via Orbited & Django pretty extensively for some of our work including the chat service & asynchronous events for eJamming.com. We went through a few alternatives to Orbited and versions of Orbited and I expect it is the leader of the pack.

Regardless, any kind of async activity going over a request/response protocol like HTTP is a nasty hack with all kinds of unexpected consequences with different software who implement the spec slightly differently. I think the long term solution is more likely to be something along the lines of what Google Wave is putting together. Behind the scenes it’s basically an extension of XMPP with transactional management. Cool ideas for a collaborative asynchronous environment like ours.

Meanwhile, Comet is here now with Orbited having a pretty stable implementation. Just be prepared to invest some significant deployment testing time before you settle on your implementation.

]]> Comment on Baconfile API by This Week’s Remainders | Geek News and Musings http://leahculver.com/2009/07/12/baconfile-api/#comment-1534 This Week’s Remainders | Geek News and Musings Sat, 01 Aug 2009 04:40:14 +0000 http://leahculver.com/2009/07/12/baconfile-api/#comment-1534 [...] Baconfile API Two handy interfaces to Amazon S3 [...] […] Baconfile API Two handy interfaces to Amazon S3 […]

]]> Comment on A is for Ajax and C is for Comet by Leah http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1533 Leah Fri, 31 Jul 2009 18:46:34 +0000 http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1533 Bastien - I'll see what I can do. I have a bunch of coding going on right now so the blog might have to wait :P Bastien - I’ll see what I can do. I have a bunch of coding going on right now so the blog might have to wait :P

]]> Comment on A is for Ajax and C is for Comet by Bastien http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1532 Bastien Fri, 31 Jul 2009 14:34:45 +0000 http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1532 It's pretty interesting to see how Comet works on the client side. It would be awesome if you wrote how to implement it on the server side. Maybe soon? It’s pretty interesting to see how Comet works on the client side. It would be awesome if you wrote how to implement it on the server side. Maybe soon?

]]> Comment on A is for Ajax and C is for Comet by cancel bubble http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1531 cancel bubble Fri, 31 Jul 2009 04:22:42 +0000 http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1531 I recently just heard about Comet so finding this article comes at the perfect time. I recently just heard about Comet so finding this article comes at the perfect time.

]]> Comment on A is for Ajax and C is for Comet by Leah http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1530 Leah Thu, 30 Jul 2009 18:41:21 +0000 http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1530 Anirudh - we didn't use Django very much for the orbited stuff which is probably why it wasn't so bad. Anirudh - we didn’t use Django very much for the orbited stuff which is probably why it wasn’t so bad.

]]> Comment on A is for Ajax and C is for Comet by Anirudh http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1529 Anirudh Thu, 30 Jul 2009 13:08:45 +0000 http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1529 Leah, Have you been able to get Orbited to work with Django? We'd used it for our project a long time ago and was able to get Django to publish messages to Orbited streams by means of a relatively ugly XML-RPC hack. I wrote about the hack on my blog <a href="http://anirudhsanjeev.org/tutorialhow-to-django-comet-orbited-stomp-morbidq-jsio/" rel="nofollow">here</a>. While I no longer work on that project, my article serves as the default reference for django+orbited on the documentation page of Orbited. Since you're a prolific django developer, I'm sure that the community would appreciate any of your suggestions on getting django and orbited to work together. Thanks, Anirudh Leah,

Have you been able to get Orbited to work with Django? We’d used it for our project a long time ago and was able to get Django to publish messages to Orbited streams by means of a relatively ugly XML-RPC hack.

I wrote about the hack on my blog here. While I no longer work on that project, my article serves as the default reference for django+orbited on the documentation page of Orbited.

Since you’re a prolific django developer, I’m sure that the community would appreciate any of your suggestions on getting django and orbited to work together.

Thanks,
Anirudh

]]> Comment on A is for Ajax and C is for Comet by Josh http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1522 Josh Sun, 26 Jul 2009 03:01:59 +0000 http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1522 Comet is some cool stuff. Hopefully one of these days I can work on a project and get to apply it. Another good server to check out is meteorserver.org Comet is some cool stuff. Hopefully one of these days I can work on a project and get to apply it.

Another good server to check out is meteorserver.org

]]> Comment on A is for Ajax and C is for Comet by Daniel Einspanjer http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1521 Daniel Einspanjer Sat, 25 Jul 2009 04:07:25 +0000 http://leahculver.com/2009/07/24/a-is-for-ajax-and-c-is-for-comet/#comment-1521 I was looking at different Comet implementations when I was developing the worldwide real-time downloads counter for Mozilla. The frustrating limitation I found with long-polling is that if the events are too frequent, it can completely overwhelm the server with rapid-fire connections from even a small number of clients. My best thought for an alternative was an implementation that had the server send a a non-buffered HTML document response that it adds events to for a reasonable period of time (say a minute) before finally ending that document. Then, the client could request the document in an iframe, parse the contents as they arrive, and when the document is finished loading, re-request it. Of course, the challenges there are that I don't think it is as straightforward to be able to consume the data as a JSON stream, and you might have trouble reading the document before the DOM is complete. If you have any pointers to a good solution for being able to deliver dozens to hundreds of events per second to dozens to hundreds of clients, I'd love to hear it! I was looking at different Comet implementations when I was developing the worldwide real-time downloads counter for Mozilla. The frustrating limitation I found with long-polling is that if the events are too frequent, it can completely overwhelm the server with rapid-fire connections from even a small number of clients.

My best thought for an alternative was an implementation that had the server send a a non-buffered HTML document response that it adds events to for a reasonable period of time (say a minute) before finally ending that document. Then, the client could request the document in an iframe, parse the contents as they arrive, and when the document is finished loading, re-request it.
Of course, the challenges there are that I don’t think it is as straightforward to be able to consume the data as a JSON stream, and you might have trouble reading the document before the DOM is complete.

If you have any pointers to a good solution for being able to deliver dozens to hundreds of events per second to dozens to hundreds of clients, I’d love to hear it!

]]>