EDIT TO CLEAR THINGS UP: I use the term "area" to mean a square which is part of a grid which controls loading of models on the client side as well as mulitplayer information. I use the term "zone" to indicate a group of "areas" (maybe 9 or 16) which are controlled one a single server and controls only multiplayer data.
I was hoping to get some info on the whole "Zones" system. I understand that this is a relatively new installment to 3dgs and one which many people shrug off as an "impossibility".
Ok let me start by giving you a bit of information about my experience. Apart from my many years experience with Web development and databases I have fairly recently (the last few years) been mucking around with 3d graphics/computer physics and more recently multiplayer games. Also i was around at A4, dropped back in for A6 and have decided to return again to the 3d game scene for A7.
I did have the shell for a 2d mmo about a year ago but i kind of gave up as the whole 2d scene was a waste of time in my opinion. I did NOT however have a very advanced "zone" system. I did have a player that could log on, get his information retrieved from the server and walk around and chat to everyone else.
My "zone" system did work in terms of only loading information about players which where in the same are as you (or adjacent areas) and did NOT send this useless information to people who were outside this range. Also on the client side all information landscape sprites etc were unloaded as the player moved away.
I use the word "areas" instead of "zones" as my areas where rather small, maybe slightly larger then the size of the viewable screen so as to have 9 "areas" loaded at all times. The only problem I can see with using the 3dgs version of "zones" is that if the player wants to have loaded the information of 2 "areas" which cross "zones" (one in one zone and one in the other), or even if the "areas" idea is not implemented, then the clent would have two options:
A: disconnect completely from one and connect the other creating a sort of "loading bar" scenario.
B: Send informaiton to both servers. This is the most desired idea although I am not 100% how well this will work with 3dgs.
Geez, that was a lot

I understand that this isn't going to happen over night but I would like to at least attempt this maybe with some of you guys helping as a learning experience if nothing else.
Thanks,
Alex
P.S. I kind of rambled on a bit but hopefully you can get what I'm at
