Abstract thread and timer handling, allow custom threading and improved
scalability
-----------------------------------------------------------------------------------
Key: MUSE-274
URL: https://issues.apache.org/jira/browse/MUSE-274
Project: Muse
Issue Type: Improvement
Components: Other
Affects Versions: 2.2.0
Environment: J2EE is especially appropriate for removing Thread's.
JCA spec can be used as an implementation for example.
Reporter: Chris Twiner
Assignee: Dan Jemiolo
Currently Muse has many seperate locations where Threads are created. This
does not work well in either a managed environment or from a scalability
perspective. Ideally the default implementation would use a thread pool, and a
J2EE impl could use JCA or commonj impls.
Issue -> Environment should have a "getWorkManager" function which allows
running of runables from the code that would normally use a thread. The actual
implementation should be configurable in muse.xml. This would allow
implementations to vary depending on requirements.
The interfaces should aim to cover the existing (and the forthcoming discovery)
functionality but not much more (i.e. provide cancelation of timertasks and
simple interval based scheduling).
It is possible to subclass the base capabilities to use different threading
models but the use of private's everywhere makes this more problematic.
Providing a pluggable interface would ease integrations.
As an aside, I'm willing to work on this if people think its a good idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
