Patrick Casey <patcasey <at> adelphia.net> writes: > > How does the tapestry engine manage engine services? > Specifically, are they pooled, instantiated on a per request basis? One > static service that all requests use?
One for all requests. > Basically if I have two threads that each do: > > IEngineService service = > cycle.getEngine().getSerice(SERVICE_NAME); > > Are they each getting a guaranteed unique instance of the > service object? Is the engine instantiating a fresh service object every > time I make this call? Plucking them out of a pool? Using only one service > object for all requests (in which case I'll have to synchronize some stuff)? Again, one for all requests. You have to synchronize the accesses yourself. -- Author of an e-Book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
