Re: [Wicket-user] tracking website usage
If you're using bookmarkable pages, you could just use a servlet filter. But that's really the same thing as processing your access logs. Another approach might be to wrap the various Link classes to log when pages are accessed. Cumbersome if you don't already have Link subclasses - which we do for access control. I'm not familiar enough with the Wicket internals. Maybe there's something easier.On 5/18/06, Frank Silbermann [EMAIL PROTECTED] wrote: If all the pages in my Wicket application extend a common base page, what are some of the ways I could keep track of the each page's popularity? I'm thinking of something I could put on the base page that, upon construction, would identify the actual subclass being constructed and add it to that class' counter in persistent storage. Have any of you done something like this? If so, how did you architect that capability?
Re: [Wicket-user] tracking website usage
class BasePage {static MapClass,Integer counter=public BasePage() {int count=counter.get(getClass().getName());count++;counter.put(getClass().getName(), count);...}} -IgorOn 5/18/06, Nick Heudecker [EMAIL PROTECTED] wrote: If you're using bookmarkable pages, you could just use a servlet filter. But that's really the same thing as processing your access logs. Another approach might be to wrap the various Link classes to log when pages are accessed. Cumbersome if you don't already have Link subclasses - which we do for access control. I'm not familiar enough with the Wicket internals. Maybe there's something easier.On 5/18/06, Frank Silbermann [EMAIL PROTECTED] wrote: If all the pages in my Wicket application extend a common base page, what are some of the ways I could keep track of the each page's popularity? I'm thinking of something I could put on the base page that, upon construction, would identify the actual subclass being constructed and add it to that class' counter in persistent storage. Have any of you done something like this? If so, how did you architect that capability?
RE: [Wicket-user] tracking website usage
Probably only in contruction. I want to know how often users are using various pages, and not the number of operations they perform on each one. (In other words, the question is, How important is this page to the users? rather than How much impact does this page have on the performance of my website?) So I guess the page constructor is the right place for it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Johan Compagner Sent: Thursday, May 18, 2006 10:55 AM To: wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] tracking website usage storing the getClass() and a counter looks to me like the best thing to do. Except is in construction only what you want or when the page is used (rendered) johan On 5/18/06, Frank Silbermann [EMAIL PROTECTED] wrote: If all the pages in my Wicket application extend a common base page, what are some of the ways I could keep track of the each page's popularity? I'm thinking of something I could put on the base page that, upon construction, would identify the actual subclass being constructed and add it to that class' counter in persistent storage. Have any of you done something like this? If so, how did you architect that capability?
Re: [Wicket-user] tracking website usage
Many ways to do it. You might even consider throwing in some AOP. Eelco On 5/18/06, Frank Silbermann [EMAIL PROTECTED] wrote: Probably only in contruction. I want to know how often users are using various pages, and not the number of operations they perform on each one. (In other words, the question is, How important is this page to the users? rather than How much impact does this page have on the performance of my website?) So I guess the page constructor is the right place for it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Johan Compagner Sent: Thursday, May 18, 2006 10:55 AM To: wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] tracking website usage storing the getClass() and a counter looks to me like the best thing to do. Except is in construction only what you want or when the page is used (rendered) johan On 5/18/06, Frank Silbermann [EMAIL PROTECTED] wrote: If all the pages in my Wicket application extend a common base page, what are some of the ways I could keep track of the each page's popularity? I'm thinking of something I could put on the base page that, upon construction, would identify the actual subclass being constructed and add it to that class' counter in persistent storage. Have any of you done something like this? If so, how did you architect that capability? --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user