Kevin Conaway wrote:
> Thanks Greg.
>
> What is the synchronization actually guarding? Can you explain the
> concurrency issues at stake here?
Kevin,
No I can't actually. It does not appear necessary.
But we are deep into the phase for building 6.1.21 and I'm loath to just
pull out synchronization when we wont have a few weeks to test it before
a release.
So please raise a JIRA and we will investigate soon after 6.1.21
If anybody has a few cycles free.... could they perhaps cast some eyeballs
over this as well and give a 3rd opinion if that synchronization is needed.
Maybe if 6.1.21 is delayed a few days, we could consider this if we are all
100% sure.
cheers
> On Tue, Sep 15, 2009 at 10:40 PM, Greg Wilkins <
gregw@...
> <mailto:
gregw@...>> wrote:
>
>
> Kevin,
>
> I would be a little loath to take out that synchronization without a
> lot more
> analysis and thought.
>
> However, it is pretty easy in Jetty to provide your own classloader,
> so you
> should be able to wrap the jetty classloader with something that uses a
> concurrentHashMap as a cache on the loadResources path.
>
> But can you raise a JIRA on us anyway for this, as this is something
> we should
> look at (albeit slowly and with consideration).
>
>
> cheers
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
