Brian,
Thank you for responding. I have already left a post in the blog
feedback, but I don't expect anything I post there to be taken seriously.
Most of what I work on in-world are scripts. I am concerned about
such things as llDetectedName and llKey2name getting confused and
making scripts malfunction. I assume that llDetectedKey would return
the correct key regardless.
It appears to me that if I create a script using viewer 1.X, it will
show as being created by Andromeda Quonset. It also appears to me
that if I create the same script using a 2.X viewer, that it will say
it was created by Andromeda Resident.
In some of my products, I have access controls based on the name of
the AV that touched the product. The script in that product will
have a notecard containing the avatar names of those AV's that are
permitted to use the product. Names being easier to work with than
keys for some people. The notecard presumably gets read into a list
within the script. The list is checked against the name that is
returned by llDetectedName to determine access. If llDetectedName
should return Andromeda Resident instead of Andromeda Quonset, and
the list only has Andromeda Quonset in it, then access won't be permitted.
list accessList; //assume names of av's that were entered into a
notecard, and subsequently read into this list
string userName;
touch_start(<file://server1/C/My%20Web%20Sites/lsl%20wiki%201/www.lslwiki.net/lslwiki/wakkaef62.html?wakka=integer>integer
num_detected)
{
userName = llDetectedName(0);
if(llListFindList(accessList,[userName]) == -1)
{
llWhisper(0,"You are not on the access list, "
+ username); //tell AV he isn't allowed to use this
}
else
{
userFunction(); //do whatever function the AV is allowed to do
}
}
It seems to me that there is going to need to be a distinctive set of
LSL functions to accompany the display names. These might include
llDetectedDisplayName, llKey2DisplayName, and llDisplayName2Key.
It also seems likely that such new functions would only get
implemented in a 2.X compiler, which is going to create an inter
operability issue, which I think would be obvious. Do you need some
examples of these?
Andromeda
At 03:54 PM 8/17/2010, you wrote:
>On Tue, Aug 17, 2010 at 2:44 PM, Andromeda Quonset
><andromedaquon...@gmail.com> wrote:
> > Andromeda Quonset groans very loudly.
> >
> > How can we get this new "feature" cancelled before it ever gets
> > implemented? Seriously. Very bad idea.
>
>In the comments on that blog post, they say there will be a public
>beta. I would:
>
>1) Come up with insurmountable problems during open beta or provide
>other convincing feedback on why you think it's a bad idea, and
>2) get it in a JIRA that's linked to that project's meta JIRA (make
>that if it doesn't exist yet - before open beta it may not) or get it
>in the blog feedback from posts like today's announcement
>
>--
>Brian McGroarty | Linden Lab
>Sent from my Newton MP2100 via acoustic coupler
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges
