[sldev] AWG: Geometric Content Creation

[Argent Stonecutter]

On 01-Nov-2007, at 12:56, Mark Burhop wrote:
> A second reason was to allow for a view of an incremental move from  
> today's SL to a future open VW (based on AWG standards).  So the  
> "Optimized" could be thought of  as SL today (or near term),   
> adding "Client Specific" could be an interim step, and eventually  
> everything becomes "Client Specific" and SL's current optimized  
> prim model is just one example of a "Client Specific" format.

The sim needs to know the prim geometry as well, or are you thinking  
of that as another client?

Really, though, from that viewpoint what you're describing as "Client- 
specific" is the general format, and the optimized geometry is the  
client-specific one.

So we're looking at something like this?

Asset database, referenced by UUIDs or URIs.
     Assets:
         Local data (data belonging to this domain).
         Remote data (data belonging to other domains, stored as URIs)
             Local cache (copies of data belonging to other domains,  
plus URI referring to original copy)
         Client-specific (optimized) data.
             Local data (optimized data created by or uploaded  
directly to this domain)
             Remote data (optimized data available from other domains)
                 Local cached copies (copies of optimized data from  
other domains, plus URI)
             Legacy data (references to data in "optimized store", by  
UUID)
Optimized store:
     Legacy asset server, referenced by UUIDs.