[Opensim-dev] Towards 0.5, what's left?

[Stefan Andersson]

Definitively a standalone application, albeit in my dream world, it would communicate with the servers thru the http interfaces, not directly into the database layers. (which probably would give out http interfaces some more TLC)
 
/Stefan



> Date: Thu, 13 Dec 2007 13:35:17 -0500> From: sean at dague.net> To: opensim-dev at lists.berlios.de> Subject: Re: [Opensim-dev] Towards 0.5, what's left?> > On Thu, Dec 13, 2007 at 03:43:04PM +0000, Justin Clark-Casey wrote:> > So to take up the webpage analogy, the serialization you're talking > > about is just the pure 'html'? The various bits of binary data which > > make up the page/prim (e.g. pngs and gifs for webpages, textures, > > scripts and sounds for second life), are represented by uris/asset ids > > in the exported xml.> > > > Just as in a 'full' webpage format, a full sl export would also export > > those resources in a separate 'package'/'region'/'directory' to which > > the asset ids could resolve.> > > > Was actual texture data exported in byte[] format before the libsl > > change? I apologise for my ignorance on this point.> > Well, two issues. First off, yes the Texture field is coming out as a> byte[]. But that is just the texturing description. The asset> representing actually used textures is in asset land, and isn't> exported.> > My recent thoughts on the save/load model is the following.> > 1. It should be a seperate program, OpenSimDump.exe (or something), so> that you can run it while OpenSim is running, or when OpenSim isn't> running, and have no fear that OpenSim might alter the data in some> way while it is coming up.> > 2. It should read OpenSim.ini for the data sources for assets and> primstorage. This would let you use 2 different OpenSim.ini files> to dump from sqlite and move everything to mysql (for instance).> > 3. It should create what it does in an on disk directory, that would> look something like:> > dump/> prims.xml> assets.xml> UUID-UUID-UUID.jp2> UUID-UUID-UUID.xyz> > Basically, appropriate metadata would end up in xml files. When> dealing with binary data we translate back to appropriate binary> files named by UUID.> > 4. It should support a mode that dumps ALL assets, or one that dumps> only assets referenced by prims.> > For right now, there will be no guaruntee of compatibility between> OpenSim revisions. I think it will take a couple of iterations before> we get an at rest definition that makes sense. I really doubt collada> is that right at rest definition, as it seems pretty heavy for what we> need (though supporting a collada import in the future would be> definitely interesting).> > I'm going to start hacking on this tomorrow, though it likely won't> finish prior to me heading away for vacation. I'll check in stuff daily> if not more frequently so other folks can look and help if they are> interested.> > -Sean> > -- > __________________________________________________________________> > Sean Dague Mid-Hudson Valley> sean at dague dot net Linux Users Group> http://dague.net http://mhvlug.org> > There is no silver bullet. Plus, werewolves make better neighbors> than zombies, and they tend to keep the vampire population down.> __________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20071220/0c880f2f/attachment-0001.html>