Looks very interesting :) This appears to be an easier way to meet most of the needs for which I was investigating Celery, since I'm not looking at massively-scalable systems, but rather just a way to have longer-running requests (e.g. onaccepts) pushed asynchronously to givers users a more responsive system & avoid browser timeouts. & also want a way to easily build a graphical scheduler which works even on Win32 service mode (which the current cron doesn't)
> It has lots of dependencies (for example RabbitMQ) This is a little unfair - whilst RabbitMQ is the recommended Broker for Production systems, there are many other supported & porting django-kombu to web2py-kombu shouldn't be hard. >Compared to celery it lacks the ability to bind tasks and workers , This isn't important to me > remotely interrupt tasks and set timeout These would indeed be useful in time :) > Please let me know what you think. I'll give it a try :) Many thanks, Fran.
