[ 
https://issues.apache.org/jira/browse/IGNITE-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-5896:
-----------------------------------
    Description: 
Implement a protocol for thin clients in other languages.
This is an umbrella ticket for all related activities.

*Overview:*
* Client connects to a socket (according to {{SqlConnectorConfiguration}})
* There is a new client type is {{SqlListenerNioListener}}
* Ignite binary protocol is used for data exchange (BinaryMarshaller)
* Protocol is stateless (though socket can be reused for multiple operations)

*Socket request message format:*
* {{uint32}} Message length
* {{uint16}} Operation code (like CacheGet or MessagingSend)
* Operation-specific data

*Socket response message format:*
* {{uint32}} Message length
* {{byte}} Success flag
* Operation-specific data or exception details

  was:
Implement a protocol for thin clients in other languages.
This is an umbrella ticket for all related activities.

*Overview*
* Client connects to a socket (according to {{SqlConnectorConfiguration}})
* There is a new client type is {{SqlListenerNioListener}}
* Ignite binary protocol is used for data exchange (BinaryMarshaller)
* Protocol is stateless (though socket can be reused for multiple operations)


> Thin client protocol
> --------------------
>
>                 Key: IGNITE-5896
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5896
>             Project: Ignite
>          Issue Type: New Feature
>          Components: platforms
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>             Fix For: 2.2
>
>
> Implement a protocol for thin clients in other languages.
> This is an umbrella ticket for all related activities.
> *Overview:*
> * Client connects to a socket (according to {{SqlConnectorConfiguration}})
> * There is a new client type is {{SqlListenerNioListener}}
> * Ignite binary protocol is used for data exchange (BinaryMarshaller)
> * Protocol is stateless (though socket can be reused for multiple operations)
> *Socket request message format:*
> * {{uint32}} Message length
> * {{uint16}} Operation code (like CacheGet or MessagingSend)
> * Operation-specific data
> *Socket response message format:*
> * {{uint32}} Message length
> * {{byte}} Success flag
> * Operation-specific data or exception details



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to