Adunh Slavy
Ammatar Trade Syndicate
   |
Posted - 2007.12.22 22:19:00 -
[1]
All the client side stuff.
Folders in peeps and places, overview settings, window positions, drone groups (if that's client side) - all of it 
If nothing else an easy thing might be to just make a backup of the client side data set on successful shutdowns, since it is just a directory and some files. Although XML or simialr would be nice so corps could share overview settings and what not for wars and such and we could import/export them.
The Real Space Initiative - V5 (Forum Link)
|
Adunh Slavy
Ammatar Trade Syndicate
|
Posted - 2007.12.23 05:09:00 -
[2]
 Originally by: CCP Explorer
Originally by: Adunh Slavy
All the client side stuff.
I would prefer a prioritised list... 
But what about server-side settings, such as ship fittings, which would allow you to re-fit a ship by importing an XML file? You could also more easily brag about your setup by posting the XML file.
I'm going to bet you get lots of answer for priorities, I'll have to give it some thought my self when there is not a bottle of beer on the desk. However à
What I suggest is, you guys start with something client side that is easily quantified like window positions. That way players can play with it and find the bugs in your parser before you allow players to start uploading god knows what to the server. I'm not trying to say your implementation will have bugs so much as all software has a bug somewhere; it's better to find them on the client than the server. I'd suggest XML as the out of the box ADO parsers from MS, as you've an MS backend, have built in buffer over run detection. I am pretty sure you do not want to suffer from the implications of such things on the first go. Additionally, there may be server side settings you do not want us players to know about that should be considered, so if you do server side exports, you will need to possibly do a transform at some layer prior to allow playing to see the export it self so that we do not get curious about interesting looking fields.
So, start with simple stuff first, get it working properly then let us mess about with more complicated data sets like the overview and then move on to server side stuff once it is safe and the implications are well understood.
The Real Space Initiative - V5 (Forum Link)
|