-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Allow custom session ids #250
Conversation
What do you think about having a single option |
Thank you for your prompt reply.
Let me clear this question before I change the code, test, and docs and commit/rebase again. |
|
Every time a new connection is made to a sockjs server, a session id is generated in the client and sent to the server. This session id helps the server distinguish connections. By default, the current code generates a random 8-character-long string as session id. There is currently no way to increase the entropy or even generate your own session ids, so this commit is an attempt to tackle that limitation by specifying the option called sessionId in the options passed to SockJS.
4f677b9
to
e668284
Compare
@brycekahle how does it look now |
Looks great! |
Thanks a lot |
By the way sorry, I don't know much about the release cycle of sockjs-client. Can you tell me when is the next release that includes this commit? Thanks |
I can try and get a new version out this week. |
Looking forward to! |
@imkira I just released 1.0.1 |
@brycekahle thanks a lot! |
Every time a new connection is made to a sockjs server, a session id is
generated in the client and sent to the server. This session id helps
the server distinguish connections. By default, the current code
generates a random 8-character-long string as session id. There is
currently no way to increase the entropy or even generate your own
session ids, so this commit is an attempt to tackle that limitation.