[sldev] [META][AWG]log chat of AWG meeting Friday, Oct 5, 2007
Argent Stonecutter
secret.argent at gmail.com
Sat Oct 6 06:40:42 PDT 2007
On 06-Oct-2007, at 02:09, Lawson English wrote:
> Lawson English wrote:
>> Friday's log-chat of the AWG meeting is now up. Feel free to
>> comment here or on the wiki.
>>
>> https://wiki.secondlife.com/wiki/Oct5_scale_rest
Very dense (high information content) material, I second the call for
a summary. :)
> My comment on my own contribution:
>
> https://wiki.secondlife.com/wiki/Talk:Oct5_scale_rest
Added a comment there too. Some kind of general asset tagging needs
to be established pretty early on, even if at first it's only used
between grids. Properties on an asset with some kind of domain key
and name. The first thing I thought of was to index it by creator-
UUID and property name, and internally or in transport use reference
compression like DNS does - instead of storing N copies of the
creator UUID for N properties, have the UUIDs be indexed by back-
reference. Maybe a separate UUID table would be better, though, since
any given asset shouldn't need too many UUIDs associated with it.
(I think better in pseudo-SQL than XML)
CREATE TABLE uuids (
uuid_num short integer primary key, -- not stored separately,
just the index of this UUID in the array.
uuid long long integer
);
CREATE TABLE properties (
domain_uuid_num short integer, -- domain that defined it, or
NULL for standard-defined properties
creator_uuid_num short integer, -- UUID of creator agent, or
NULL for domain-global
permissions short integer, -- bitmap, includes flags for
things like whether other domains should allow it to change
name varchar,
value varchar,
UNIQUE (domain_uuid_num, name) -- primary key
);
Having the key for the property include the creator domain will avoid
namespace collisions and let the standard add required properties
without worrying about whether some random domain has used that name
already. Permissions are of course discretionary, but are also hints
as to whether the property will be ignored when the asset returns to
the originating domain.
More information about the SLDev
mailing list