You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/09/15 11:13:00 UTC

[jira] [Commented] (IGNITE-5896) Thin client protocol

    [ https://issues.apache.org/jira/browse/IGNITE-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167721#comment-16167721 ] 

Pavel Tupitsyn commented on IGNITE-5896:
----------------------------------------

Initial part done. {{ignite-5896}} merged to master: {{a00052e94531528c5df0dc4485d8882514b40af4}}.

> 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
>             Fix For: 2.3
>
>
> 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
> * {{uint32}} Request id
> * {{byte}} Flags (compression, etc)
> * {{uint16}} Operation code (like CacheGet or MessagingSend)
> * Operation-specific data
> *Socket response message format:*
> * {{uint32}} Message length
> * {{uint32}} Request id (value from above)
> * {{byte}} Flags (success, compression, etc)
> * Operation-specific data or exception details



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