We've got server-side object container streaming, server meshing and the persistence database refactor. Is there an order to these?

Yeah, so the object container streaming on the server is happening now, and the persistence stuff is being worked on. The tasks are happening in this coming quarter and the quarter afterwards. And then the first stage of the meshing is in some ways hand in hand. Because the problem is, even if you're streaming on the server and you don't load everything in, if I have players that are in 50 different locations and they've hit every area of the content, that server will have had all those areas streamed in. So it's going to be spending the same amount of processing power that it's currently spending right now, if the players distribute themselves all over the place. So the way it really becomes effective is when you say, you as a server, you're only really focusing on this area, and then it only has that part of the area loaded in. So the server object container streaming will come pretty quickly together with that aspect of it. You've got to have the streaming aspect there so you can just load in this place. But then what you need beyond that is the handoff mechanism, so a ship can hand off from one server, say, taking care of Hurston, to the server taking care of general space, to the server taking care of ArcCorp, for instance. But I would say expect to see the persistence changes come... I mean, go take a look at the roadmap, but these are all things that we're working towards this year.