And you can always switch it off/on at runtime thru an admin page for example.
On Thu, May 26, 2011 at 10:44 PM, Martijn Dashorst <martijn.dasho...@gmail.com> wrote: > On Thu, May 26, 2011 at 9:34 PM, Brown, Berlin [GCG-PFS] > <berlin.br...@primerica.com> wrote: >> Is the request logger invasive? Is it something that can be used in a >> production environment? >> >> http://www.volkomenjuist.nl/blog/2009/04/08/wicket-requestlogger/ > > Only when you log the size of the session. That costs time (needs to > serialize the session on each request). If you also set the number of > requests stored to a low number, there's little to no overhead. > > We are running the requestlogger since it was crafted (2007 I recall) > and never had any problem with it. > > Martijn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
