If your concern is with GIL it should be fairly easy to make a version of asyncjob on multiprocessing, for more difficult would be to prevent issues might happen on the code that the developer will run in the separate process. Just keep in mind that asyncjob is meant for short term tasks and on production you will probably start more that one process of your application. Starting more than one process will result in having multiple execution queues (one for each process) which greatly reduces the side effects of having the GIL in place.
If otherwise the concern is having a separate process that handles all the requests using a task queue it's probably a better solution but requires a separate tool. On Mon, Nov 26, 2012 at 7:44 PM, kgk <[email protected]> wrote: > http://pypi.python.org/pypi/**tgext.asyncjob<http://pypi.python.org/pypi/tgext.asyncjob> -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
