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
