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

Are we suppoed to only use a specific version of the client-side socket.io.js library? #27

Open
akarelas opened this Issue Feb 20, 2013 · 4 comments

Comments

Projects
None yet
3 participants
@akarelas

akarelas commented Feb 20, 2013

When I used the most recent version of the library in my application, I would get a new GET request to /socket.io/1/?t= exactly every 15 seconds... plus a few messages that I've disconnected on Firebug.

When I switched to the client-side library provided in the examples/chat folder of PocketIO, this behaviour stopped, and I don't get new GET requests every 15 seconds, and I'm not getting messages that I've disconnected either.

Are we suppoed to only use a specific version of the client-side socket.io.js library?

@vti

This comment has been minimized.

Show comment
Hide comment
@vti

vti Feb 21, 2013

Owner

Maybe they've changed something. I haven't checked that for awhile.

Owner

vti commented Feb 21, 2013

Maybe they've changed something. I haven't checked that for awhile.

@akarelas

This comment has been minimized.

Show comment
Hide comment
@akarelas

akarelas Feb 21, 2013

It's ok, as long as you mention it in the documentation if that's the case.

akarelas commented Feb 21, 2013

It's ok, as long as you mention it in the documentation if that's the case.

@BlueT

This comment has been minimized.

Show comment
Hide comment
@BlueT

BlueT May 2, 2013

@akarelas did you get the problem solved? Would you like to share how did you deal with the problem?
I have the same problem for a long time, didn't care about that but now I'm going to use PocketIO on production project and I'm affraid that would cause problems...

BlueT commented May 2, 2013

@akarelas did you get the problem solved? Would you like to share how did you deal with the problem?
I have the same problem for a long time, didn't care about that but now I'm going to use PocketIO on production project and I'm affraid that would cause problems...

@vti

This comment has been minimized.

Show comment
Hide comment
@vti

vti May 2, 2013

Owner

I suggest using SockJS. Currently working in production. Feels great!
02.05.2013 9:07 пользователь "BlueT - Matthew Lien - 練喆明" <
notifications@github.com> написал:

@akarelas https://github.com/akarelas did you get the problem solved?
Would you like to share how did you deal with the problem?
I have the same problem for a long time, didn't care about that but now
I'm going to use PocketIO on production project and I'm affraid that would
cause problems...


Reply to this email directly or view it on GitHubhttps://github.com/vti/pocketio/issues/27#issuecomment-17321976
.

Owner

vti commented May 2, 2013

I suggest using SockJS. Currently working in production. Feels great!
02.05.2013 9:07 пользователь "BlueT - Matthew Lien - 練喆明" <
notifications@github.com> написал:

@akarelas https://github.com/akarelas did you get the problem solved?
Would you like to share how did you deal with the problem?
I have the same problem for a long time, didn't care about that but now
I'm going to use PocketIO on production project and I'm affraid that would
cause problems...


Reply to this email directly or view it on GitHubhttps://github.com/vti/pocketio/issues/27#issuecomment-17321976
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment