Potential disconnect event needed for anonymous users

[rclai]

The connectionIdle event triggers instead.

Is this a browser issue?

Edit: Oh, if I'm logged in, and I close the window tab, then the connectionLogout event triggers, but if I'm not logged in and I close the browser, connectionIdle triggers.

Should there be a connectionClose event, given that idling is arguably qualitatively different than closing?

[mizzao]

Interesting that connectionIdle is triggered at all. Sounds like a bug that I should probably look into.

The connection is still deleted, though; is that right?

[tsega]

@mizzao I have a similar problem, closing browser for either authenticated or anonymous users doesn't do anything. However, for authenticated users, closing tabs triggers the connectionLogout event but not for anonymous users.

To overcome that, I looked for a solution to set non-logged in users as logged in users temporarily so that the connectionLogout event would fire. I found the accounts-guest package that logs in anonymous users but I'm having problem with that, it's not working at all.

I'm going through all of this, just to see who's viewing a certain page/route for both types of users. Any suggestions?

[mizzao]

Okay, I see the problem here; the connectionLogout is not triggered unless there is a userId, while the connectionIdle triggers regardless and should behave consistently:

https://github.com/mizzao/meteor-user-status/blob/master/status.coffee#L133

What do you guys think should happen in this case? Both events should be triggered?

[mizzao]

Actually, I just looked at this again and it is by design. A connectionLogout is only triggered when a user's authenticated connection either logs out or disconnects. If the user pushes the "Log Out" button, there is no second connectionLogout when their now-unauthenticated connection disconnects.

I don't think connectionIdle should be triggered regardless, but I could look into it.

Can you guys clarify what you are doing that would need to watch unauthenticated users disconnect?

In @tsega's use case, we could implement something similar to #28 with a weak dependency on Iron Router.