Leo Simons wrote:
It's interesting to see what happens if you remove the support/requirement for release semantics. You can still implement singleton semantics, per-thread semantics, per-lookup semantics, fixed-number-of-multithreaded-object semantics, and the like.
Which is what I think we should be moving to.
But you cannot do transparent pooling, nor can you put javax.sql.Connection instances (or similar) in your service manager.
But you can design to take this into account.
And at the end of the day I think its better to deal with things that have specific release considerations as dedicated service interface.
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
