Name |
Description |
AppAttachReqAns |
|
AttachReqAns |
|
Destination |
|
DestinationData |
|
ErrorResponse |
|
FetchAns |
The response to a successful Fetch request is a FetchAns message containing the data requested by the requester. The FetchAns structure contains a series of FetchKindResponse structures. There MUST be one FetchKindResponse element for each Kind-ID in the request. |
FetchKindResponse |
The FetchAns structure contains a series of FetchKindResponse structures. There MUST be one FetchKindResponse element for each Kind-ID in the request. see RELOAD base -12 p.95 |
FetchReq |
The Fetch request retrieves one or more data elements stored at a given Resource-ID. A single Fetch request can retrieve multiple different kinds. see RELOAD base -12 p.92 |
ForwardingHeader |
|
ForwardingOption |
|
JoinReqAns |
|
LeaveReqAns |
|
MessageFragment |
|
MessageTransport |
|
PingReqAns |
|
RELOAD_MessageBody |
|
ReloadDialog |
|
ReloadMessage |
|
ReloadMessageFilter |
|
SecurityBlock |
The third part of a RELOAD message is the security block. The security block is represented by a SecurityBlock structure see base -19 p.52 |
StoreAns |
In response to a successful Store request the peer MUST return a StoreAns message containing a series of StoreKindResponse elements containing the current value of the generation counter for each Kind-ID, as well as a list of the peers where the data will be replicated by the node processing the request. see RELOAD base -12 p. 90 --alex |
StoreKindResponse |
In response to a successful Store request the peer MUST return a StoreAns message containing a series of StoreKindResponse elements containing the current value of the generation counter for each Kind-ID, as well as a list of the peers where the data will be replicated by the node processing the request. see RELOAD base -12 p.90 |
StoreReq |
A StoreReq message is a sequence of StoreKindData values, each of which represents a sequence of stored values for a given kind. RELOAD base -12 p. 86 --alex |
UpdateReqAns |
|