User Tools
Page Tools
Site Tools
technology:web-protocol
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
technology:web-protocol [2013/09/07 19:19] Pinkgothic created |
technology:web-protocol [2017/11/18 15:34] (current) |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| It //requires// a handle from the client, a client software identifier, the protocol version used by the client and the IP of the server, along with the name of the requested resource (latter quite akin to HTTP). | It //requires// a handle from the client, a client software identifier, the protocol version used by the client and the IP of the server, along with the name of the requested resource (latter quite akin to HTTP). | ||
| - | It //permits// two [[technology:avatar]] 'prototypes' per connection that are sent on initial connection with the server: One 'human appearance' that by unhacked neural connectors is auto-rendered as 'offline appearance', one 'preferred avatar' that can be freely designed. They can be ''REQUEST''ed again by the server (if they've expired in cache or were otherwise lost to it, or for any arbitrary reason), or ''UPDATE''d while connected. The client //can// refuse to send either, following any hail to do so. The server //can// refuse to render either for any reason, or //alter// the prototypes as it sees fit for any duration it sees fit. | + | It //permits// two [[technology:avatar]] 'prototypes' per connection that are sent on initial connection with the server: One 'human appearance' that by unhacked [[technology:neural connector|neural connectors]] is auto-rendered as 'offline appearance', one 'preferred avatar' that can be freely designed. They can be ''REQUEST''ed again by the server (if they've expired in cache or were otherwise lost to it, or for any arbitrary reason), or ''UPDATE''d while connected. The client //can// refuse to send either, following any hail to do so. The server //can// refuse to render either for any reason, or //alter// the prototypes as it sees fit for any duration it sees fit. |
| The data format of the avatar prototype data is not defined by the protocol, but the de-facto established standard format contains meta-data, quick-access to avatar dimensions and quirks (computation of latter is especially arduous). The format's meta-data is fairly free-for-all, much like the XML format of today, and MMORPG avatar creation kits tend to populate avatars with a //lot// of extra information about properties (e.g. magic spells and comparable) that let the avatar interact non-physically or long-range with the environment, **something it does //not// inherently support**. (In plain English: Most servers will expect your avatar to be self-contained and with a hard surface. If your avatar deviates, it depends heavily on the experience and willingness of the server to permit those traits.) | The data format of the avatar prototype data is not defined by the protocol, but the de-facto established standard format contains meta-data, quick-access to avatar dimensions and quirks (computation of latter is especially arduous). The format's meta-data is fairly free-for-all, much like the XML format of today, and MMORPG avatar creation kits tend to populate avatars with a //lot// of extra information about properties (e.g. magic spells and comparable) that let the avatar interact non-physically or long-range with the environment, **something it does //not// inherently support**. (In plain English: Most servers will expect your avatar to be self-contained and with a hard surface. If your avatar deviates, it depends heavily on the experience and willingness of the server to permit those traits.) | ||
technology/web-protocol.1378581575.txt.gz ยท Last modified: 2017/11/18 15:34 (external edit)
