3.4le birlikte server meshinge yavaştan başlıyolar
*Q:"What will be the extent of the first pass on the server meshing planned for 3.4 ?"*
> Clive Johnson: "For the first-pass version we'll probably divide the Stanton system into sections and have one server manage each section. So we might have a Port Olisar server, another for Yela, and so on. Migration between servers would only happen as players QT from one location to another (although if you had the patience to do so you would also be able to fly between servers at sub-quantum speeds). We won't be connecting game servers across server regions (US, EU, etc) in this version. It also seems likely that each server region will still have multiple instances of the Stanton system.
> Obviously this is a much simplified implementation compared to what we eventually want to achieve but it is still complex enough that we will need to deliver several key pieces of the technology. First among these is the ability to connect multiple game servers in the same simulation. Next, seamlessly transitioning entities and clients between servers. We'll also need changes to our backend services to keep track of which players are on which server and determine when they need to transition to another. The services may also have to handle spinning up and shutting down new game servers on demand, as we'd like to avoid running a server for a section (e.g. Daymar) unless some players are actually there. Finally, game code will most likely have to undergo some changes to ensure that things like missions and the economy continue to function correctly even though the entities involved may be spread among multiple servers.
> Once the initial version has been put through its paces we will continue to improve and refine the technology with future pre-alpha releases, incrementally bringing us closer to the final goal of a single shard universe."nbk