You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Ryan Sonnek <ry...@gmail.com> on 2008/02/25 17:00:20 UTC
Re: Monitoring Wicket using JAMon
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 <jc...@gmail.com> 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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Monitoring Wicket using JAMon
Posted by Ryan Sonnek <ry...@gmail.com>.
I'd be happy to help if you need any since I commit to a few separate
wicketstuff projects, but applying for your own commit access would
probably be best.
On Mon, Feb 25, 2008 at 10:45 AM, lars vonk <la...@gmail.com> wrote:
> I would be glad to contribute something. Are you related to the
> wicketstuff project? Or should I just appy for commit access as
> described on: http://wicketstuff.org/confluence/display/STUFFWEB/Home.
>
> Cheers, Lars
>
>
>
> On Mon, Feb 25, 2008 at 5:00 PM, Ryan Sonnek <ry...@gmail.com> wrote:
> > 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 <jc...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Monitoring Wicket using JAMon
Posted by lars vonk <la...@gmail.com>.
I would be glad to contribute something. Are you related to the
wicketstuff project? Or should I just appy for commit access as
described on: http://wicketstuff.org/confluence/display/STUFFWEB/Home.
Cheers, Lars
On Mon, Feb 25, 2008 at 5:00 PM, Ryan Sonnek <ry...@gmail.com> wrote:
> 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 <jc...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org