I wasn't proposing using pubsub at all for either solution. :) But, if
you're building a dashboard, then you could subscribe to the connect
and close events. Use redis-cli and run MONITOR to peek at the
internals.
I'd still persist connection count in Redis separately.
INCR statusserver:connections
DECR statusserver:connections
Daniel Shaw
@dshaw
On Tue, Aug 28, 2012 at 12:30 PM, Ryan Curtis <
wedn...@gmail.com> wrote:
> or are you explicitly publishing to pubsub on user connect?
>
>
> On Tuesday, August 28, 2012 3:26:44 PM UTC-4, Ryan Curtis wrote:
>>
>> Ok, that sounds viable, but the devil's in the details... I'm working on a
>> statusserver that is another
socket.io server using the same redis store.
>> How can it get notifications that someone connected on another server? Does
>> a connection message show up via pubsub when a user connects?