At St Mary's Shaftesbury we use Firefly for our VLE.  I won’t give you a sales pitch on Firefly, but suffice to say, that after a bit of a journey from Moodle through SharePoint we have rested at Firefly – quite simply, at this point in time (history has taught me that things can change!), this product, the company and their approach to IT, is nothing short of excellent.  I like Firefly; I like the chaps and chapesses at Firefly!

Apart from having an extremely intelligent approach to the design of their product, they also invite you to “dig” into the system, and do magic things yourself, if you are so inclined – my type of IT product.

Over recent months, we have indeed done a fair bit of customisation, some reasonably advanced and some not so – a lot of this customisation has involved implementing improved integration with our MIS system (Schoolbase) – more on that in future blog posts!

One feature that we did have in our previous SharePoint system, which was surprisingly popular, and in many ways greatly missed – was an “online users” section.  So this is how I set about building this into Firefly.

Creating the online users module

The main intention was to make this feature as portable as possible, without the need to change any core structural feature of Firefly – as such the only area that did require a slight alteration, was to create a nonclustered index on the Hits table, based on a descending date field – this was run past the Firefly team, who agreed that it shouldn’t have any negative impact.

The main reason for this requirement, is that the Hits table is massive (literally millions of rows in our instance) – and without this index, the performance of the appropriate SQL query would be unacceptable.

Index creation screenshot:


Server Side

Once the Hits table was indexed efficiently, the next stage was to create a server side process, which would query the Hits table (and perform any necessary filters to limit the users being displayed – for example not to show any parents who may also be online etc). This was achieved by creating an aspx page located in a sub folder of the plugins folder on the server (e.g. “Plugins \ ClientASPXFiles \ STMWhoOnline.aspx”).

This aspx page utilises the Firefly security model, so that you cannot browse to it as an unauthorised user etc.

The process reduces the count to show only the latest ten users, ordered by date descending, based on the most recent top 500 rows in the Hits table – because technically it is not known as to how many hit’s an individual user is going to create, and it is impractical to query the entire Hits table, an arbitrary figure of the last 500 hits, gives a good chance of getting at least the last 10 unique users http hits, without causing unnecessary strain on querying the entire table.

The page then uses some basic array and looping procedures to ensure that it is only displaying a single latest instance per user.

The final top ten results are then returned in a json format, which can easily be read by a client side script making an ajax call.

Finally, to make the server side query as efficient as possible, the page is actually set to cache all results every 10 seconds, so that if multiple users are online, the server is not querying unnecessarily (tens of times per second etc) causing drain on server resources.

Client Side

All that is required on the client side, it a small snippet of JavaScript to create an ajax call every 10 seconds, polling the server file (created above) and then presenting the json returned from this file in a standard html <li> element, with an <a href> hyperlink to the users profile, and a hover tooltip displaying the actual date/time of the most recent “hit”.

This JavaScript is placed by literally adding a Firefly formatted text component, and then using the code editor – copying in the JavaScript.


This process works remarkably well, and when using an SQL profiler, with the query reduced to only take the top 500 hits and the utilising of caching, the SQL load is exceptionally efficient.

Technically, there is a theory that by only querying the last 500 hits, you cannot be scientifically absolute in stating that you are getting all the last top ten individual users (e.g. one user may clock up 300 hits by themselves etc), but in our tests, this proved to be more than adequate and indeed does always appears to show the most recent top ten.



As an addition, I have also adjusted our query accordingly to create other “more secure” pages, for administrative purposes only, to establish currently logged on parents etc – this was in many ways more enlightening from an IT perspective, than the knowledge of the school users – indeed we were quite astonished to establish, that there were parents logged onto the portal almost constantly!

  Share Post