[Opensim-dev] Proposal to eliminate the name, description and invType fields from the assets db

[Stefan Andersson]

Again, I don't see why we need to have assetId === sha-1 hash - if the only thing we want to accomplish with it is de-duping, we just make sure to send the hash along, and any context can choose to use it to de-dupe or not.
 
And to trust it or not.
 
Obviously, you wouldn't trust an assetId generated by an untrusted source to represent the asset binary anyway, so quite a lot of re-hashing and checking will be done along the way anyway.
Best regards,Stefan AnderssonTribal Media AB Join the 3d web revolution : http://tribalnet.se/ 


Date: Mon, 23 Jun 2008 15:59:39 -0400From: teravus at gmail.comTo: opensim-dev at lists.berlios.deSubject: Re: [Opensim-dev] Proposal to eliminate the name, description and invType fields from the assets db table
I'm not convinced the SHA1 UUID will be extensible enough to allow for future plans.   The idea is to not assume anything with a UUID.  Adding assumptions increases scalability at the cost of extensibility.
 
Best Regards
 
Teravus 
On 6/23/08, Melanie <melanie at t-data.com> wrote: 
Hi,Sean Dague wrote:> I don't understand how your approach deals with sniffing the wire or the> cache, finding the asset UUID, and just embedding that in you items or> scripts.It doesn't. Because that approach is not enjoying blanket coveragein the DMCA. Means, in the case of UUID sniffing, each _item_ is aseparate violation, subject to a separate takedown order. Yes, oneper prim!If the texture is re-uploaded, blanket protection applies.The law isn't always common sense - in fact, it mostly diverges fromcommon sense!> Anyway, it's a little moot for right now, as the current system is> there.  But I really think the way forward involves us using a hashing> strategy.  Once we dig in there, we'll see how hard it would be to make> UUID generation runtime configurable.  And keep this in mind.I'm happy if that concern is not forgotten. That is all I wanted,recognition of this as a valid concern, so no decisions are madethat could ultimately lead to an entire grid being judicially shut down.Melanie_______________________________________________Opensim-dev mailing listOpensim-dev at lists.berlios.dehttps://lists.berlios.de/mailman/listinfo/opensim-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20080623/5e94fa1f/attachment-0001.html>