Thanks Shawn, this is very helpful. It's good to hear Orbited is being actively developed again.
I'm not already using RabbitMQ for anything, so I'm going to take the opposite approach: start out doing some test projects with Hookbox, and then try porting them to Orbited. I'm completely new to Comet-style development, so Hookbox's simplicity appeals a lot to me, and so does its approach to integrating with the rest of one's application stack as a primary design goal. Basically, I'm less confident about Hookbox as a robust solution, but it seems like a lower upfront cost for where I am, and I'm more confident that I won't get lost in the infrastructural implementation details and write bad code. Hopefully I'll then be able to smoothly port whatever I've done to Orbited. Looking forward to hearing how things go for you, and seeing your blog post. I'll definitely report back as well. -Ethan On Sat, Jan 15, 2011 at 10:23 AM, Shawn Milochik <sh...@milochik.com> wrote: > Ethan, > > Thanks for the reply. Since this isn't something a lot of people are doing > I'm going to make my own way and report back. I just wanted to ensure I > wasn't straying from what the community at large was doing, but since > there's no consensus I'll just do whatever. > > In my research yesterday, including a friendly chat in the #orbited IRC > (freenode), here are the things I found: > > Hookbox does more, but is heavier. > Orbited is once again under active development. > It's possible to use Orbited with Celery and RabbitMQ. > Hookbox replicates some functionality of Celery and RabbitMQ. > > Based on this, and the fact that I'm already using django-celery and > RabbitMQ, I'm leaning towards Orbited. I'm going to put together a little > test project this weekend. If all goes well I'll probably stop there and > just use Orbited. I'll put up a blog post with relevant code snippets. If > something goes horribly wrong, or I get tremendously motivated, I'll do the > same with Hookbox and have a better understanding of the differences. > > Shawn > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
