Ticket #1394 (new defect)

Opened 2 years ago

Last modified 3 months ago

Bind the scheduler to the WSGI app

Reported by: alberto Assigned to: anonymous
Priority: normal Milestone: 1.5
Component: TurboGears Version: 1.0.4b3
Severity: normal Keywords: sprint scheduler
Cc:

Description

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

Change History

05/24/07 06:43:22 changed by alberto

  • keywords set to sprint scheduler.

12/19/07 04:51:42 changed by Chris Arndt

  • version changed from trunk to 1.0.4b3.

06/06/08 09:30:36 changed by faide

  • milestone changed from 1.1 to 1.1.1.

08/24/08 10:27:19 changed by faide

  • milestone changed from 1.6 to 1.5.