I'll improve it soon. On Tue, Aug 30, 2011 at 9:15 AM, Emond Papegaaij <[email protected]> wrote: > You are right. We have 548 RequestMappers registered and for an url starting > with 'wicket/page', wicket scans through all but 3. Setting the score to > something higher than 0 will prevent 545 mapRequest calls for every page > instance maping. > > Best regards, > Emond > > On Monday 29 August 2011 21:07:12 Martin Grigorov wrote: >> Hi, >> >> Currently the compatibility score of PIM and BM is 0 so that users' >> mappers have priority. I think this is a bit wrong because mounting >> more pages in YourApp#init() will increase the time to get to PIM's >> mapRequest(). >> Most of the time stateful apps work with PIM because every callback >> url is processed by PIM (e.g. >> wicket/page?3-1.IBehaviorListener-form-button) >> I.e. there is no need to ask N MountedMappers before PIM when the >> chance that the request is for PIM is quite high. >> >> I suggest to make its #getCompatibilityScore() logic the same as >> BufferedResponseMapper, i.e. if the request url starts with >> 'wicket/page' then the score should be high (Int.MAX_VALUE). >> I see no problems with that for small apps but I see big gain for apps >> like Topicus' with 1000+ page (@Topicus devs: are they mounted pages?) >> >> The same is valid for BM. >> >> What do you think ? >
-- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
