Skip to content

Feature Request: Documentation #28

carlskii opened this Issue Mar 4, 2014 · 5 comments

3 participants

carlskii commented Mar 4, 2014

Please provide description for each of the URL within the tornado-celery/ example.

@mher mher added the enhancement label Mar 4, 2014
AlJohri commented Apr 9, 2014

+1 :)

AlJohri commented Apr 13, 2014

@mher I don't entirely understand how tornado-celery consumes tasks.

I was reading this blog post to try to understand the various methods of integrating celery and tornado.

It seems to me that tornado-celery provides an HTTP API for interacting with celery tasks but there's no easy way to notify the main tornado app when a task completes with polling -- is this correct?

AlJohri commented Apr 13, 2014

As I'm reading further, I see that tornado-celery uses pika for a non-blocking AMQP client and supports using send_task or apply_async with a non-blocking producer.

Is there any way to set up a non-blocking consumer? I'd like to be able to utilize my tornado eventloop (or perhaps another tornado eventloop in a separate process) to perform non-blocking tasks that simply scrape web pages. What's the easiest way to make this happen?

AlJohri commented Apr 13, 2014

Okay so I see that tcelery maintains its own ioloop,

In my module, can I create an @celery.task that uses @gen.coroutine

        http_client = AsyncHTTPClient()
        response = yield http_client.fetch("")


mher commented Apr 20, 2014

I've setup documentation for tornado-celery at Feel free to send pull requests.

@mher mher closed this Apr 20, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.