ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-5896) Thin client protocol
Date Wed, 02 Aug 2017 09:57:00 GMT

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

Pavel Tupitsyn edited comment on IGNITE-5896 at 8/2/17 9:56 AM:
----------------------------------------------------------------

Added {{uint32 requestId}} to the protocol, so that client can match response in future multithreaded
scenarios.


was (Author: ptupitsyn):
Added {{uint32}} requestId to the protocol, so that client can match response in future multithreaded
scenarios.

> 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
> * {{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)

Mime
View raw message