There is a flaw in session ID generation that causes to create same session ID for two different clients connected at
the same time.
[One more note: Ben told me that the session ID generation is random - there is a high chance on duplicate depending
how random seeds are initialized; also it is pseudo-random function specific).
We have an application that creates 1 ephemeral node of the following form:
where <host:port> is specific to the node where the application runs and is retrieved using gethostbyname, and the
value of 'connected' is set to the current time (as returned by time function).
We have many applications, however lets consider application A and B that are connecting from 2 hosts: A from
rz502425:8080 and B from llf520108:8080.
Log in to post a comment.