Hi all, just a quick question...
Once a Tapestry service implementation gets instantiated, and that
service's status moves to "realised", at what point does that
implementation get destroyed?
Tapestry instantiates a service implementation the first time a service
method gets called, and I'm just wondering whether the reverse is also
true - eg. released for garbage collection if no method has been called
after a period of time.
In some cases it's needed for a service to retain state, such as keeping
a 'static final' map of connected users. This is thread safe, but would
be lost without a single service implementation instance.
Regards,
Chris.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
