Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #1394 (closed defect: wontfix)

Opened 12 years ago

Last modified 11 years ago

Bind the scheduler to the WSGI app

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


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.


Change History

comment:1 Changed 12 years ago by alberto

  • Keywords sprint scheduler added

comment:2 Changed 12 years ago by Chris Arndt

  • Version changed from trunk to 1.0.4b3

comment:3 Changed 11 years ago by faide

  • Milestone changed from 1.1 to 1.1.1

comment:4 Changed 11 years ago by faide

  • Milestone changed from 1.6 to 1.5

comment:5 Changed 11 years ago by mramm

  • Status changed from new to closed
  • Resolution set to wontfix

In multi-app, multi-process deployments you want an external scheduler.

And I'm not sure why you wouldn't want one scheduler per process in a multi-app single process app.

Note: See TracTickets for help on using tickets.