>>The retrieving of the profiles info is done in my page that deals with all users info/roles >where it doesn't make sense. I'm not sure why no one really caught the problem before and >why the developers of this provider thought that we may want to update the last activity >date on the data retrieval (and also implemented this in SP as well). Sounds very strange >to me.
>
>If you need to record the last activity date - that is, the last time a user hit any page on your site, how would you do it? Last activity basically implies every page hit.
>
>Updating this everytime you retrieve a user's profile is pretty reasonable. If it was broken out into it's own method, you now require two hits to the database: onces to get the data, and the other to update the last activity date.

I see the point here but there is a problem - looks like every time you access any profile data from any place you get last activity date updated. In my case I was building a web page for Roles/Users management - in this case I definitely don't need to Update Last Activity date.

So, what may be a good solution here (to be able to update activity date for the current user when he hits a page) and not invoke this method more times than necessary?

In the current implementation with the code commented by me the original Login get updates the User's activity, but that's it.