search

secondlife / jira-archive

2 stars 0 forks source link

[BUG-41103] Feature Request: New URI namespace /legacyname #12689

Open sl-service-account opened 7 years ago

sl-service-account commented 7 years ago

Information

We currently have no text-only uri namespace that returns an agent legacy name regardless of the "View Display Names" viewer setting.

This feature request is for a new uri namespace path /legacyname for the secondlife:///app/agent/ tree.

Unlike the /about and /inspect paths, /legacyname will return an agent's legacy name regardless of the "View Display Names" viewer setting and will NOT generate a clickable url.

Operation Example:

With "View Display Names" disabled, secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/inspect returns "Lucia Nightfire" as a clickable url secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/about returns "Lucia Nightfire" as a clickable url secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/legacyname returns "Lucia Nightfire" as text

With "View Display Names" enabled: secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/inspect returns "Lucy daughter of the Devil (lucia.nightfire)" as a clickable url secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/about returns "Lucy daughter of the Devil (lucia.nightfire)" as a clickable url secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/legacyname returns "Lucia Nightfire" as text

Thanks in advance for any consideration.

Links

Related

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-41103 | | Summary | Feature Request: New URI namespace /legacyname | | Type | New Feature Request | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Lucia Nightfire (lucia.nightfire) | | Created at | 2016-12-24T03:06:09Z | | Updated at | 2017-02-01T19:29:56Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2017-01-04T13:22:43.667-0600', 'How would you like the feature to work?': 'We currently have no text-only uri namespace that returns legacy name regardless of the "View Display Names" viewer setting.\r\n\r\nThis feature request is for a new uri namespace path /legacyname for the secondlife:///app/agent/ tree.\r\n\r\nUnlike the /about and /inspect paths, /legacyname will NOT be dependent on the "View Display Names" viewer setting and will NOT generate a clickable url.\r\n\r\nOperation Example:\r\n\r\nWith "View Display Names" disabled,\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/inspect returns "Lucia Nightfire" as a clickable url\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/about returns "Lucia Nightfire" as a clickable url\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/legacyname returns "Lucia Nightfire" as text\r\n\r\nWith "View Display Names" enabled:\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/inspect returns "Lucy daughter of the Devil (lucia.nightfire)" as a clickable url\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/about returns "Lucy daughter of the Devil (lucia.nightfire)" as a clickable url\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/legacyname returns "Lucia Nightfire" as text\r\n\r\nThanks in advance for any consideration.', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'Target Viewer Version': 'viewer-development', 'Why is this feature important to you? How would it benefit the community?': '?', } ```
sl-service-account commented 7 years ago

Oz Linden commented at 2017-01-04T19:22:44Z

How are the existing inspect and about uris used?

sl-service-account commented 7 years ago

Lucia Nightfire commented at 2017-01-04T22:53:58Z

The inspect and about uri's perform multiple tasks all-in-one.

When used in chat or dialogs they synchronously resolve an agent key by replacing it with an agent name without the overhead of using the script function llRequestAgentData() and subsequent dataserver() event. They double as a url that can open an agent profile upon click.

This performance allows applications to store and/or use only keys instead of both keys and names in communications. This performance means applications do not have to rely on the script function llRequestAgentData() and subsequent dataserver() event which is significant overhead when communications are involved.

This request is for a new uri /legacyname to perform similar to the namesakes of /displayname & /completename which do not generate url's, but still resolve the agent key into a formatted name.