Capabilities

The viewer (and other client applications) can request capabilities from the simulators to gain access to certain features.

• Map from public URL to private URL
  • e.g. https://sim1001:12041/cap/uuid1
• Cap set <map><key>Asset upload</key>

  <uri>URI1</uri>

  <key>Seed capability</key>

  <uri>URI2</uri>

  </map>

• Viewer knows public URL
• Internally, backbone stores both public and private URL

Flow for getting capabilities

• Viewer contacts login server requesting a particular capability
• Login server contacts sim
• Sim contacts backbone, sending a private uri corresponding to an action or service
• Backbone generates and returns a public uri corresponding to the private uri

Notes:

• Do not rely on the form of a capability, other than it must be http: or https:. Capabilities from the same source needn't point to the same host or port, and the path needn't start /cap.
• To get a list of the capabilities that the latest Second Life client is requesting, use this command:

wget -q -O - https://bitbucket.org/lindenlab/viewer-release/raw/9296ce32f98a6ad9f1c6404d16645245ffe454f0/indra/newview/llviewerregion.cpp | grep 'capabilityNames.append' | sed 's/^[ \t]*//;s/capabilityNames.append("//;s/");//'

See also: Tao Takaishi's blog discussion of capabilities