Persistent key-value storage to share script URLs

[Qie Niangao]

Golly. It's so obvious, but somehow I only just realized it.

One problem that's been an ongoing annoyance is the ephemeral nature of addresses obtained via llRequestURL. It makes purely in-world HTTP communications really difficult, demanding either an external registry / directory service, or fallback to internal out-of-band email.

But lo, the persistent key-value store appears a perfect way to share those URLs among all the communicating scripts that support the experience.

(I can anticipate an objection that the persistent store is all the communications one could want, but not really. It's kinda the shm to HTTP's semaphores. Kinda.)

[Dolphin Linden]

I would strongly suggest that any configuration data for your Experience be kept in the kv system. LR uses a script which reads all the settings from a notecard and updates the db appropriately. Things like messaging channels and script load pins are very important to keep secret, so if you put them in the kv storage they are not leaked even if the script is leaked.