While working on a patch to simplify current Jetspeed code, two ideas
came up on me:
1- DynamicURI is a strong candidate for pooling instances, since it
should be heavily used under most setups (typically, we have more than
five per request, and they are instantiated afresh in every request). I
imagine you have already considered this object.
2- It could give an efficience boost if we could change the way it is
used. Instead of returning it as a String, we could have something like
dynuri.write( data.getWriter() ); , writing it straight into the
response. This would save some StringBuffer and String instantiations
---> less garbage ---> better memory efficience again.
I don't know if this second idea is feasible to implement with
templating engines like velocity, jsp taglibs or the pull approach. So I
wanted, before doing further experiments, to know what do you experts
think about it. :-?
Looks promising?
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
