Hi Claude,
> It's more an optimisation than a new feature. So all people having high
> traffic sites could benefit of it.
>
> For instance, you could have a pool of, let's say, twenty instances of
> the ParameterParser tool -with a reinit() method- instead of recreating
> one at each request.
>
> In most cases (whenever it makes sense), it is far faster to only
> re-initialize an object than to have to instanciate it from scratch.
I guess I just don't have any experience with object instantiation as
a performance issue. (DB processing and the request/response across
the network were far more significant in the total when measured.)
> > Sorry, but I'm not quite getting it. How would one use it? The <url
> > regexp>, I mean.
>
> This is also meant at providing some optimization. Tools with such a
> scope would be request tools that are instanciated if and only if the
> url of the request matches the regexp provided in the toolbox.xml. It
> seems to me that this approach is far better MVC than the
> $toolLoader.loadTool("thetool") approach.
>
> For instance, a SearchTool can be put in the context only if the url is
> like /search/*.vm
Oh, I get it now. It's a condition to determine whether to put the
tool in the Context or not, right?.
> In fact I am more or less ready to code those suggestions, but I wanted
> to somehow discuss the specs here so it get more chances to get commited
> as is.
Hey, that's great!
Best regards,
-- Shinobu
--
Shinobu "Kawai" Yoshida <[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]