Currently, a restarting process makes it look like all users left the space and then came back.
In order to resolve this, a possible solution would be to give clients the ability to include an id param in their request URL. This would have been passed back to them in an identify message from the Longhouse server. Then, Longhouse would not create a new presence key for them, but rather update the existing one.
[x] Send "identify" event back to client
[x] Accept "id" parameter in URL for constructing new client
[ ] Return new "id" if passed "id" has expired Not necessary
[x] Revert f2eb79ab
[x] Persist request ID to client separately (perhaps only in in-memory register)
Currently, a restarting process makes it look like all users left the space and then came back.
In order to resolve this, a possible solution would be to give clients the ability to include an
idparam in their request URL. This would have been passed back to them in anidentifymessage from the Longhouse server. Then, Longhouse would not create a new presence key for them, but rather update the existing one.Return new "id" if passed "id" has expiredNot necessary