Unexpected behavior when the Session host leaves the session

asked 2015-08-03 11:38:23 -0700

Sushma1990 gravatar image

updated 2015-10-20 17:17:19 -0700

praveenb gravatar image

According to the information given in the link https://allseenalliance.org/framework... , when a session host leaves, the session continues to exist and the remaining participants can continue to communicate. But when this scenario was tried and the session host was disconnected, all the other joiners in the session were also removed from the session and they could not communicate with each other. SessionMemberRemoved( ) call back was used to track the members that left a session.

What is the exact expected behavior when a Session Host leaves?

edit retag flag offensive close merge delete


you might try on the core mailing list. https://lists.allseenalliance.org/mailman/listinfo/allseen-core

ry.jones ( 2015-08-07 11:58:36 -0700 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2015-08-10 01:36:40 -0700

praveenb gravatar image

updated 2015-10-20 16:58:26 -0700

The key point when a multi-point session host leaves is, how it leaves.

If you are using bundled applications throughout your scenario and exit the application hosting the multi-point session, the following two things happen:

  • Session host leaves the multi-point session
  • Routing node (that is truly hosting the multi-point session under the covers) exits bringing down all connections

If a routing node hosting the multi-point session exits, all other joiners are removed from the session.

If you call LeaveSession from the session host and let the routing node bundled with the application continue to run, you should observe the behavior mentioned at the link you referred.

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

1 follower


Asked: 2015-08-03 11:38:23 -0700

Seen: 96 times

Last updated: Oct 20 '15