Difference between revisions of "User:Burhop Piccard/Geometry Based Architecture View"
Jump to navigation
Jump to search
m |
m (→Communication) |
||
| Line 7: | Line 7: | ||
=Communication= | =Communication= | ||
[[Image:Geomcomunication.gif |Overview]] | [[Image:Geomcomunication.gif |Overview]] | ||
Communication between components is represented by red arrows. This is expected by be carried out by a internet based Rest protocol and defined by the AWG. | |||
The requirement from the geometry perspective varies depending on the path. Third party applications wanting to upload data to an asset server would value thoughput over latency and granularity. | |||
Communication with the viewer requires minimum latency and greater control of the input stream. Initially, the protocol needs to support existing Second Life Geometry (Prims, sculpties) but needs to be extendable to new SL data types as well as External data types. | |||
=Components= | =Components= | ||
Revision as of 17:05, 30 October 2007
Overview
Communication
Communication between components is represented by red arrows. This is expected by be carried out by a internet based Rest protocol and defined by the AWG.
The requirement from the geometry perspective varies depending on the path. Third party applications wanting to upload data to an asset server would value thoughput over latency and granularity.
Communication with the viewer requires minimum latency and greater control of the input stream. Initially, the protocol needs to support existing Second Life Geometry (Prims, sculpties) but needs to be extendable to new SL data types as well as External data types.
Components
Third Party Components
Persistant Storage
Viewer
