On Thu, Aug 19, 2010 at 9:43 AM, Aidan Thornton <makos...@gmail.com> wrote:
> On 8/19/10, Kelly Linden <ke...@lindenlab.com> wrote: > > I just wanted to point out that this theoretical new user's username > would > > be baloo198731, it would not be baloo198731.resident. The 'Resident' > isn't > > really a part of a new user's identity. It is only shown to viewers that > do > > not support display names and legacy LSL script calls - in other words > that > > last name is only there when required for backwards compatibility. > > > > Which has the interesting side-effect that you can't trivially convert > from a username to a legacy full name since there are two different > possible conversions and no way of telling which is correct without > accessing the login database, right? > > There is no such thing as a legacy full name for non-legacy accounts. We tack on a 'Resident' last name when required for compatibility with viewers that do not understand display names and legacy LSL calls, but it is not a part of their name. But in essence you are correct. You can go from a 'full name' to a 'username' but not as easily the other way - though parsing for a '.' is likely to get you pretty good results. If you have the UUID (which you should in both viewer code and LSL) you can get whichever name you want - username, full name or display name. - Kelly
_______________________________________________ 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
