Global instances only to an app
Reported by bahuvrihi | February 12th, 2009 @ 08:17 AM
Currently global instances (Task.instance) are truly global; one-per task class. This makes them tricky in the context of threaded apps; and breaks the model of apps owning all the resources they use.
Global instances should only be global per-app. Each app has it's own globals. This fits with the model that only allows tasks that belong to a particular app to be enqued and executed by that app.
Comments and changes to this ticket
-
bahuvrihi May 3rd, 2009 @ 09:01 AM
- Assigned user set to “bahuvrihi”
- State changed from “new” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
A framework for making configurable, file-based tasks and workflows.
bahuvrihi