THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Geode is a reliable distributed data management tool. There is a demand to access Geode from various programming languages. But the existing client-server protocol is too complex to understand, and it’s not even documented. That establishes the need for a new client-server protocol.
...
Protocol Terms
Any binary protocol will require following things
Version: This indicates the api API version.
Command Id: This indicates api API needs to invoke.
Request Id: This helps to relate request-response.
Object Type: What is the type of serialized object.
Error Handling: It indicates the problem with api API invocation.
Streaming support: To support the large response or continuous response.
Command Format: Api request and response.
Byte Order(Big Endian)
Connect
The new protocol will be integrated with current Geode server. The new client driver can connect with Geode server by sending byte “110”.
Command Id
Following command(RequestTypes) will be supported
| MetaDataConfigRequestType | 1 |
MetaDataConfigRequestType = 1
AuthenticationRequestType = 2
PutRequestType = 3
GetRequestType = 4
PutAllRequestType = 5
GetAllRequestType = 6
FunctionRequestType = 7
CreateRequestType = 8
InvalidateRequestType = 9
DestroyRequestType = 10
KeySetRequestType = 11
ValuesRequestType = 12
EntrySetRequestType = 13
ContainsValueForKeyRequestType = 14
ContainsKeyRequestType = 15
ContainsValueRequestType = 16
RemoveAllRequestType = 17
SizeRequestType = 18
PutIfAbsentRequestType = 19
RemoveIfValueIsSameRequestType = 20
ReplaceIfValueIsSameRequestType = 21
ReplaceIfValueExistType = 22