So my idea, so to speak, is to share the hosting between clients, and reserve a slot for the authoritative server (xbox). And I'm wondering what everyone's thoughts on this are, latency, error-prone considerations, fundamental flaws, things of that nature...
Say xbox [a] is the server, it has 2 lobby's of 20 clients it must provide for. I'm thinking that each client has built-in server hosting code, just like a lobby system for any popular fps nowadays would. And since only 32 people can be connected at any one time, have the master-host, xbox [b], capable of shifting control to another user when they exit the game. In this setup, I'm visualizing having the xbox [b] connect simultaneously to the xbox [a] for routine cleanup and authoritative validation, and then disconnecting so that other lobby's containing another 20 clients can do the same, and therefore never exceed the 32 limit.
The only problem with such an idea, is that in for instance, an MMO game, only 32 people would be visible at any one time, and they may or may not be part of the lobby the client in debate is connected to. Which is quite problematic (characters phasing in and out of existence, pausing mid-animation... etc).
So if anyone has any ideas to best mine, or any ideas at all, I would definitely enjoy the read.
The end goal I have is to provide MMO content using a master-xbox for database transactions, and eventually using SteamWorks to combine xbox and pc users. So I imagine you can see the problem here, given Microsoft does not provide any networking facilities other than Live, nor dedicated servers for game logic.
Edited by themeow, 28 September 2012 - 07:58 AM.