-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aixen server model #5
Comments
That looks like the XBL server model... But good idea, masters can be my servers. |
It's ok, but for connecting with the emulator? I think we need some modifications to the emulator |
The modifications will be made later. |
Aixen will have a library which will allow various things, including the On Thursday, March 13, 2014, Jano Varga notifications@github.com wrote:
NOTICE: This e-mail (and any attachments) may contain PRIVILEGED OR |
The main difference is that the xbl model just has server clusters in On Wednesday, March 12, 2014, Jano Varga notifications@github.com wrote:
NOTICE: This e-mail (and any attachments) may contain PRIVILEGED OR |
So why mot to be simplystic like them? (I know, we dont have so much powerful servers..) |
As im looking... Oh my english... 💃 |
Here's the general flow of how, say two players ( Players I & II:
Random (first) master:
Pinged (selected) master:
Slave:
|
I was wondering... @haneefmubarak Doesn't this implies that the user can only play with the ones on the same slave? It might be a good idea, so that the ping is always the lowest possible, but the slave must contact other slaves to obtain their playerlist, and order these queries to others servers based on the latency this user has in regard to them. So, the client should send the ping results, shouldn't it? The system might even get more complicated if we add some features (ie, matchmaking prefers friends, or the same language, level, or what else...) |
Well, the slave would actually talk to the master for matchmaking, so it isn't restricted to players on the slave only. Messaging and sync are distributed across the slaves of the players. |
I like the idea of latency sorted matching, but instead of having the client and the ping, slaves would probably point the player instead. |
I think that we don't need the master servers to be connected and that we can make the protocols binary anyways. |
additional research questions:
|
Here's a rough idea of what I have so far:
Sorry about the graph being messy and all. Anyways, essentially, the diagram shows:
Some stuff that the diagram doesn't show particularly well:
The text was updated successfully, but these errors were encountered: