Why?
On 6/6/06, Henri Dupre <[EMAIL PROTECTED]> wrote:
I was wondering if it would be possible/a good idea to add request
synchronization inside the framework to prevent concurrent accesses.
The idea would be to prevent two pages to be rendered concurrently unless
specified (maybe have somekind of page annotation @NonSynchronized). I bet
in 90% of cases this is not a good thing. Of course this can be added as a
servletfilter or other kind of filter, but this would be better at a lower
granularity since the only critical part is the page rendering.
Also it wouldn't be a good idea to prevent concurrent accesses to the asset
service.
Thanks,
Henri.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
