
| Key: |
SVC-2508
|
| Type: |
Meta Issue
|
| Status: |
Open
|
| Priority: |
Normal
|
| Assignee: |
Unassigned
|
| Reporter: |
Argent Stonecutter
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Relates
|
|
|
|
This issue is related to by:
|
|
|
SVC-1406 Non-volatile storage for meta-information
|
|
|
|
 |
|
SVC-701 Copyright/license/notes fields on assets, to allow proper attribution and provide license and configuration information.
|
|
|
|
 |
|
SVC-92 llInstantMessageLocal() function for long-distance communications
|
|
|
|
 |
|
SVC-1115 General "attributes" for accounts
|
|
|
|
 |
|
SVC-2509 Communication bus for scripts and viewers
|
|
|
|
 |
|
SVC-550 Reserved chat channels for LSL->client communication.
|
|
|
|
 |
|
SVC-3848 Script-to-viewer communication: llViewerSay, llViewerOwnerSay, llViewerInstantMessage
|
|
|
|
|
|
SVC-109 There is no way to safely serialize a list, a new function is needed.
|
|
|
|
|
|
|
This is a meta-issue to cover in-world, primarily short-distance communications and state sharing between scripts, between custom viewers, and between scripts/objects and custom viewers.
There are a plethora of special purpose communication channels, both obvious and otherwise, that components of systems can use to communicate. There's no overall communication design, so you have llInstantMessage for communicating between objects and avatars, llSay(and friends) and listens for broadcast communications, and link messages for broadcasts local to a linkset.
What we don't have are point-to-point messages between objects, point-to-point or broadcast messages between viewers or between viewers and objects, or passive information sharing between object or viewers.
This meta-issue is linked to a variety of proposals for in-world script-view-agent communications.
|
|
Description
|
This is a meta-issue to cover in-world, primarily short-distance communications and state sharing between scripts, between custom viewers, and between scripts/objects and custom viewers.
There are a plethora of special purpose communication channels, both obvious and otherwise, that components of systems can use to communicate. There's no overall communication design, so you have llInstantMessage for communicating between objects and avatars, llSay(and friends) and listens for broadcast communications, and link messages for broadcasts local to a linkset.
What we don't have are point-to-point messages between objects, point-to-point or broadcast messages between viewers or between viewers and objects, or passive information sharing between object or viewers.
This meta-issue is linked to a variety of proposals for in-world script-view-agent communications. |
Show » |
| There are no comments yet on this issue.
|
|