Hi, Glad it worked.
I have something similar in my application, but instead of using a RequestFilter I use a PageRenderRequestFilter.
This is only called for pages and has the added benefit of giving you easy access to the page name, parameters, etc.
There's something similar for component events, ComponentEventRequestFilter, in case you'll ever need that, by the way.
-Filip On 2008-08-14 10:05, Otho wrote:
Thank you very much for the answer. Works perfectly! But this brought up a new question. The UserActivityFilter is used to track a users last activity to check for "active users at the moment". The simplistic approach I use at the moment updates a database table with a reference to user and a timestamp. Using a requestfilter then obviously leads to a lot of database roundtrips per user-activity, since every asset triggers the filter. How would you track useractivity in a real world application? A resolution of about 1 minute would suffice, but it shouldn't be much above that. Regards, Otho
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
