on 5/29/01 8:53 PM, "Sky Torch" <[EMAIL PROTECTED]> wrote:
> thanks.
>
> sometimes, it may be hard to make a service reentrant, e.g. some
> state info, if there is, need to protected by exclusive locks.
>
> isn't it going to cause performance bottleneck in high volumn system? i.e.
> the service is being requested heavily in the system.
Not at all. This isn't any different than how a servlet engine would cache
an instance of a Servlet. In fact, if you think about it, a Service is no
different than a Servlet except that it is managed by Turbine instead of the
Servlet engine. The same is true for Turbine Modules: ie: Screens, Actions,
Navigations, Pages, Layouts.
> doesn't it improve the performance by having some service instance pool
> instead of singleton ?
Huh?
A Service instance IS by definition, a singleton because the ServiceBroker
caches the instances of a Service.
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
