* This is a HUGE OMG update and will definitely have unknown side effects.. so this is really only for the strong hearted at this point. Regular people should let the dust settle.
* This has been tested to work with most basic functions. However.. make sure you back up 'everything' before using this. It's that big!
* Essentially we're back at square 1 in the testing phase.. so lets identify things that broke.
The following patch makes some enhancements to loading/saving the Xml2
format.
- Add streamed version of functionality for saving prims to Xml2
format. The streamed version (optionally) allows for saving the
prims whose positions appear within a particular bounding box.
- Expose stream versions of LoadPrimsFromXml2 and SavePrimsToXml2 in
the Scene class
- Extend loading from Xml2 (the streamed version) to optionally start
scripts for the loaded scene objects)
* WARNING: Until both regions upgrade to this revision, prim crossings from regions on this revision to earlier region revisions will not work properly
* e.g. in the attachments cases, the attachments will remain visible but won't be individually detachable
* This change may seem to have more costs than benefits, but I'm doing it because I can soon reuse this changed existing code in another context - it seems better not to
proliferate similar but slightly different xml serializations.
* I think this has been done cleanly from inspection and testing, but if prim creation or load suddenly starts playing up more than usual, please open a mantis
* This also has the effect of stopping the archiver generating ghost in-world prims
* Some code dupliction also removed
* Adding to a scene is now parameterized such that one can choose not to actually persist that group
* This is to support a use case where a module wants a scene which consists of both objects which are persisted, and ones which are just temporary for the lifetime of that server instance
