Message type to store value at the keys root
Author: Ingmar Baumgart
The following diagram shows usage relationships between types.
Unresolved types are missing from the diagram.
The following diagram shows inheritance relationships for this type.
Unresolved types are missing from the diagram.
BaseCallMessage (packet) |
A basic Remote-Procedure-Call message |
Name | Type | Description |
---|---|---|
srcNode | NodeHandle |
source node |
id | uint32_t |
the id to identify multiple date items with same key and kind |
statType | int |
message type for stats |
authBlock | AuthBlock[] |
optional authentication block containing a signature |
nonce | unsigned int |
nonce to match RPC responses to corresponding calls |
isModifiable | bool |
true, if the data item may be overwritten by other nodes |
value | BinaryValue |
value that has to be stored on keys root |
type | int |
message type |
ttl | int |
time to life |
key | OverlayKey |
overlayKey that corresponds with value |
kind | uint32_t |
the kind of the stored data item |
// // Message type to store value at the keys root // // @author Ingmar Baumgart // packet DHTputCAPICall extends BaseCallMessage { OverlayKey key; // overlayKey that corresponds with value uint32_t kind = 1; // the kind of the stored data item uint32_t id = 1; // the id to identify multiple date items with same key and kind BinaryValue value; // value that has to be stored on keys root int ttl; // time to life bool isModifiable; // true, if the data item may be overwritten by other nodes }