Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not using a heartbeat #10

Open
bernatfortet opened this issue Sep 4, 2013 · 3 comments
Open

Not using a heartbeat #10

bernatfortet opened this issue Sep 4, 2013 · 3 comments

Comments

@bernatfortet
Copy link

Hey guys,

Just found this: http://stackoverflow.com/questions/13544333/how-to-track-the-number-of-anonymous-users-server-side-in-meteor

Since meteor uses sockets, in my opinion, it is much reliable and elegant to use a socket closing event to determine presences.

Did you already took a look at this? Do you think it's worth implementing?

@tmeasday
Copy link
Owner

tmeasday commented Sep 4, 2013

I did consider using the socket connection but, to be honest, I can't really remember why I abandoned that method.

Coming at it fresh, I would ask the following questions:

  1. Can we know the userId of the user based on their socket connection?
  2. Can we attach data to the connection (Prescence.state) ?

Let me know if you find out more -- definitely worth investigating again I think.

@bernatfortet
Copy link
Author

Hey, I've just found this package: https://github.com/mizzao/meteor-user-status
They use sockets to define the presence of the user.
It's works really well and also adds a couple of events for when a user logs in and out.

@snshn
Copy link

snshn commented Sep 6, 2013

I believe it's worth a shot.
It surely will become much faster, using sockets, while consuming less http traffic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants