Hello,
I'm writing an app based on Turbine. This thing basically
does the following:
* Lots of screens that the users fill with some data.
* The screens are sent through Turbine to a transactional
service (think MQSeries).
* The answers from the transactional service are processed,
and the output is sent back to the screens.
In this context, I will have several objects with different
lifetimes:
1. A "system" object that must be alive while the server is
processing requests; a Singleton, used by all interactions.
2. A "session" object that must be alive while a user is logged
on. If the user logs off, or the browser session times out,
the object is destroyed.
3. Other transient objects.
I know how to handle (3), and Turbine provides a way to handle
(2) by associating my "transactional session" object with the
concept of a session handled by Turbine.
The question is, what is a good way to handle (1)? Where do I
put the line
System system = new System(...);
so that this object will be alive while the server is up? Any
other considerations I should keep in mind? Hints?
Thanks in advance,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
