#1394: Bind the scheduler to the WSGI app
------------------------+---------------------------------------------------
Reporter: alberto | Owner: anonymous
Type: defect | Status: new
Priority: normal | Milestone: 1.1
Component: TurboGears | Version: trunk
Severity: normal | Keywords:
------------------------+---------------------------------------------------
This is another module globals related issue... ATM, we can only have one
scheduler per process. If two or more TG apps should cohabitate nicely in
the same process, we need that the scheduler is app specific.
The general solution to this problem would be to bind it at the
{{{turbogears.globals}}} StackedObjetProxy, something like
{{{turbogears.globals.scheduler}}}.
Wrappers at scheduler.py to proxy to this app-local scheduler for
backwards compatibility.
Alberto
--
Ticket URL: <http://trac.turbogears.org/ticket/1394>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" 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-tickets?hl=en
-~----------~----~----~----~------~----~------~--~---
