Skip to content

Is there really no way to guarantee correct connection count? #129

@FOMNick

Description

@FOMNick

I followed the connection roster example and it seems to work great aside from a a quirk:
Over time, I found that my session counts were getting out of whack. Forcing a restart on the juggernaut process while my Rails server is running produces a subscribe event, but never an unsubscribe event in the event that the juggernaut server goes down. The session count is completely unchecked by a corresponding unsubscribe event in this scenario. Is there any way to combat this issue?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions