Hi Christian,

I'm planning to implement something like this soon but I hadn't really planned on making it role driven. I would like to do something  like DotNetNuke and have how many users online, newest user, new users today etc.

I generally never use session state for anything unless I absolutely have too and I don't think its needed here. In the membership api there is Membership.GetNumberOfUsersOnline() that counts based on last activity of the user and a window of time configurable in siteSettings.

My plan is to create a SiteStats class and cache it with say a 5 minute cache timeout (configurable from web.config). We can call this membership method to get the count but in order to keep it more up to date we may need to add a few more siteUser.UpdateLastActivityTime() statements in a few places. Like probably in Default.aspx.cs if the user is authenticated we can call this for every page view. We can also have a file cache dependency and invalidate the cache when a new user logs in or out.

Not sure if this will meet your needs since you are talking about specific roles but maybe it can be extended.

Joe

I don't see anything in Membership for that. in mojoMembershipProvider the implementation is actually calling methods on SiteUser, this keeps it abstracted well so any db can be used so I would say we can add the needed method to SiteUser. Which db are you using? I can stub out a method for this on SiteUser and as soon as svn is back up I'll commit it or you can take this and implement it using similar logic to the count procedure then send me the changed files.

using System.Collections;
using System.Collections.Generic;
using System.Collections.ObjectModel;
 
public static Collection<SiteUser> GetUsersOnlineSince(int siteID, DateTime sinceTime)
{
    Collection<SiteUser> users = new Collection<SiteUser>();
 
    // TODO: code to populate collection goes here
   // retrieve a reader and populate new siteUser obejcts and add to collection
 
 
    return users;
}

We just need to get all the dbs implemented for the next release but we can start with the one you need.

Joe

Another option is instead of populating the collection like I previously suggested, you could just return the reader and bind to the reader, instead of creating all those user objects.

The more I think of it this is the most lightweight and more consistent with other things in mojoPortal. Generic collections are pretty cool but its extra overhead to create all those objects just for data binding, readers are much lighter.

Joe