Hi,
Our distributed caching provider module requires that you have a caching cloud to connect to (AppFabric and Memcached connectors are provided by default), and to configure your cluster in the client settings section.
Additionally, you also have to identify explicitely the keys or regex patterns for objects you want to distribute and to configure dedicated strategies accordingly. This is because many cached object won't serialize, thus the default strategy is not enabled for distribution.
There are logging and training mechanisms, which may help you with that, but honestly I start thinking it may be a bit overkill for your current concerns (might be helpful for scaling up later on though).
I will look into updating the multiple connections provider to add DB relying capabilities, and I will come back to you.
Cheers
PS: I have juste enabled attachments for the current forum.
OK I have been looking for a solution, but neither the DNN integrated UsersOnline component nor the native asp.net Membership provide a way to track client source, only the last activity date.
Accordingly, I suppose that getting the distributed caching provider to work still is the easiest solution, since relying on DB would then require to develop a dedicated system similar to the UsersOnline component, which would take a significant time.
I also realized the detection provider requires a few updates to fully support that scenario.
I'm currently applying the updates, and we'll provide you with an update ASAP.
In the mean time, may I suggest you start looking to adding an AppFabric caching cluster to your web farm? You don't need AppFabric to be installed on multiple servers, only if you wish to enable high availibility caching.