Early WhosOnCFC 2.2.0 Alpha Released to Testers

Today I managed to get the code cleaned up well enough to be released to a select few testers.  There are still a few problems that need to be addressed in the alpha, but nothing really serious.

The first issue is how bots are now tracked if the showBots configuration setting is enabled.  On the average, I would say my site gets around 300 visitors every 24 hours and only a handful of those are actual visitors.  The remaining visits come from bots and crawlers.  On a busy site I would imagine this number would be much higher.  If that information is tracked for the full 24 hour period it could be eating up a huge amount of memory.  My thinking is they should be tracked for 4 to 6 hours before their session information is purged.  I am open to any suggestions any of you may have on this.

The other issue I am dealing with is how it handles clients that visit after their session has timed out but has not been removed from the session list.  This may not be a problem for most folks, but some of my web sites use WhosOnCFC for user authentication.  Generally WhosOnCFC tries to match a session/client ID to one in the active user array.  If it finds a match it returns the active user index where it found the ID, otherwise it returns zero meaning the user is a guest.  While it may not be a big deal if you are using session-based management, it could potentially be very interesting if you are using client-based management.  At any rate, it is something I am looking into and it will be resolved before a public release.

I also removed the objectfactory.cfc from the code.  Since everything is wrapped up in one component, IoC/dependency injection is no longer an issue.  I know at least one person who should be a little happier.

Well, that is pretty much all I have for now.  I hope everyone has a happy and safe weekend.