On Sat, Mar 6, 2010 at 1:52 AM, Rob Nelson wrote:
> I haven't dug deep enough yet to fully grasp what is going on in
> LLSelectMgr, but it seems to me that it would be a lot more efficient to
> simply attach the permissions with each object's properties when they
> are sent to the client by the se
Rob Nelson wrote:
> Consider a user in a sandbox who wants to clean up his mess. If he were
> using a viewer based on LibOMV, all the viewer would have to do is loop
> through the region's object dictionary and return/delete objects that he
> owns. In the LL viewer (correct me if I'm wrong), LLSe
On Sat, Mar 6, 2010 at 1:17 PM, Boroondas Gupte
wrote:
> Rob Nelson schrieb:
>> Consider a user in a sandbox who wants to clean up his mess. If he were
>> using a viewer based on LibOMV, all the viewer would have to do is loop
>> through the region's object dictionary and return/delete objects th
The whole approach to objects and assets needs to change anyway, because of
interop. Interop is a process --- it doesn't appear suddenly out of
nowhere, you have to pave the way by evolving your code into a more flexible
form.
There is an implicit assumption in the viewer that everything is store
Boroondas Gupte schrieb:
> The mini-map colors objects you own differently, so there must be
> another way to get at least owner information.
>
The server sends two bits with each prim that defines ownership.
One bit is the owner bit, it is set if the current agent owns the prim.
The other is th
Rob Nelson schrieb:
> Consider a user in a sandbox who wants to clean up his mess. If he were
> using a viewer based on LibOMV, all the viewer would have to do is loop
> through the region's object dictionary and return/delete objects that he
> owns.
How does LibOMV obtain/build that dictionary?
>
While working on my viewer's object handling stuff, I happened across a
rather fundamental flaw in the SL viewer's architecture.
When one considers filesystem permissions or even database permissions,
you notice that permissions are generally attached to the object that a
user attempts to access,
