And for 1.4+ we could make that map concurrent if that isnt already the case
On 12/02/2009, Thomas Mäder <[email protected]> wrote: > The synchronizationn is around a HashMap lookup. Considering how much longer > it takes to actually process a request, I very much doubt that there is much > contention. Modern VM's are MUCH better at handling slight contention (like > 2-4 contending threads) than older VMs. Don't worry! > > Thomas > > On Thu, Feb 12, 2009 at 7:12 AM, ywtsang <[email protected]> wrote: > >> >> at 1.3.5 >> >> class: org.apache.wicket.protocol.http.request.WebRequestCodingStrategy >> method: urlCodingStrategyForPath >> >> the variable "mountsOnPath" is synchronized >> is this necessary? >> >> because the WebRequestCodingStrategy is initialized once by "request cycle >> processor", which in turns is shared by all requests (i read this at >> Wicket >> In Action) >> >> so synchornized the "mountsOnPath" can produce a big lock contention >> problem >> if we have many requests at the same time? >> >> >> -- >> View this message in context: >> http://www.nabble.com/question-about-adding-%22synchronized%22-on-mountsOnPath-at-WebRequestCodingStrategy-tp21970542p21970542.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Thomas Mäder > Wicket & Eclipse Consulting > www.devotek-it.ch > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
