The idea behind this is to create a system that will allow "viral sessions" to exist. If an Admin of a session wishes, they can enable a session setting that will tell clients they are allowed to advertise to any session they wish. Meaning a session formally hosted on a single session server can be joined by another user who will take pseudo ownership of that session for their session servers.
This idea isn't really thought through very well as of right now, but I'd figure I might as well start making notes about this idea. The current implementation in my head is a security nightmare. How does this outside session server know the information it is getting is legitimate since it's coming from someone else?
An alternative approach is to have clients inform a session host of a session server, and the session host will automatically preform all of the requirements to advertise a "guest" instance on the separate session server. This idea requires much more thought, consideration, and planning!
The idea behind this is to create a system that will allow "viral sessions" to exist. If an Admin of a session wishes, they can enable a session setting that will tell clients they are allowed to advertise to any session they wish. Meaning a session formally hosted on a single session server can be joined by another user who will take pseudo ownership of that session for their session servers.
This idea isn't really thought through very well as of right now, but I'd figure I might as well start making notes about this idea. The current implementation in my head is a security nightmare. How does this outside session server know the information it is getting is legitimate since it's coming from someone else?
An alternative approach is to have clients inform a session host of a session server, and the session host will automatically preform all of the requirements to advertise a "guest" instance on the separate session server. This idea requires much more thought, consideration, and planning!