when client_1 receives a stream that is published by client_2
everything seems to be ok.... but when the clients close the
application and then reopen it, a problem occurs when they try to
create and connect new streams: they can't see the streams
published by the other client. What kind of problem could this be?
I am wondering if there is a stratus's cache.
if you are using a web service to coordinate/communicate/look
up the peerIDs, perhaps you are getting cached responses instead of
fresh ones. we have seen that behavior in our development; our
sample app inserts a timestamp into the request to make each one
unique specifically to avoid cached results.