Summary:
Adds custom data to the session context storage.
Request specification:
Name |
Min/Max |
Type |
Description |
|
|
|
|
|
|
|
|
|
|
|
Session ID. |
|
|
|
User data. |
|
|
|
|
|
|
|
Key. |
|
|
|
Value. |
|
|
|
|
|
|
|
|
Returns:
OK/Error
Description:
The request accepts the supplied key-value pair(s) and adds it to the session context storage. You may choose your own names for the keys and you may store any type of data you require. The data will stay in the storage for as long as the session exists and can be retrieved during that time by using the get
call. To modify an existing key value, use the key name and a new value. To delete the value, leave the value
element empty (this does not remove the key from the storage but only changes the value to an empty string). Once the session is destroyed, the data is discarded.
Example:
Input
<packet version="4.0.0" id="2">
<target>sessionm</target>
<data>
<sessionm>
<put>
<session_id>vzl.40000.c60e1c63-cf1f-467a-ad68-e9261ac3c22d.14c446863b2t7e87</session_id>
<data>
<key>mykey</key>
<value>c29tZSB2YWx1ZQ==</value>
</data>
</put>
</sessionm>
</data>
</packet>
Ouput
<packet id="15c44686876t390c" version="4.0.0">
<origin>sessionm</origin>
<session>vzl.40000.c60e1c63-cf1f-467a-ad68-e9261ac3c22d.14c446863b2t7e87</session>
<data>
<sessionm>
<ok/>
</sessionm>
</data>
</packet>