I've been looking at doing something similar to this in my application. any thoughts on contributing this to a new wicketstuff project?
On Thu, Jan 31, 2008 at 9:14 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > > > > I am not sure if I follow you here. What do you mean by testing two > > pages? Here is how I think it works (and want it to work): > > > > 1. User clicks on component on Page1 that will result in navigating to > > Page2. In this case JAMon shows: Page2 30ms. > > 2. User clicks on component on Page2 that will result in a refresh > > (ajax or not) of Page2. IN this case JAMon shows: Page2 30 ms. > > > > > yes in situation 2 you are testing page2 completely, so the request phase > (handling of the click event) > and the response phase (the render of page2) > > but in situation 1 you are testing the request phase of page1 (the click > event) > and then the rendering of pag2 (thats the respond) > > And it all depends what takes a lot of time, is it the render because loads > of new data is queried from the db > with loads of stuff on the page. Or is it the action that does a heavy query > or other backend action? > > johan > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
