[jira] [Commented] (IGNITE-6607) Thin client: protocol documentation

2018-01-17 Thread Prachi Garg (JIRA)

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

Prachi Garg commented on IGNITE-6607:
-

[~dmagda], Please review the following pages:

[https://apacheignite.readme.io/docs/binary-client-protocol]

[https://apacheignite.readme.io/v2.3/docs/binary-client-protocol-key-value-operations]

[https://apacheignite.readme.io/v2.3/docs/binary-client-protocol-sql-operations]

[https://apacheignite.readme.io/v2.3/docs/binary-client-protocol-binary-type-operations]

https://apacheignite.readme.io/v2.3/docs/binary-client-protocol-cache-configuration-operations

 

 

 

> Thin client: protocol documentation
> ---
>
> Key: IGNITE-6607
> URL: https://issues.apache.org/jira/browse/IGNITE-6607
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Prachi Garg
>Priority: Blocker
> Fix For: 2.4
>
>
> Document thin client protocol on Apache Ignite readme.op:
> * Common message format (length, flags)
> * Data types (endianness, strings, etc)
> * Request/Response format for each message type
> * How to connect
> A list of supported commands can be taken from here:
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/platform/client/ClientMessageParser.java
> The protocol documentation format can be similar to REST API:
> https://apacheignite.readme.io/docs/rest-api



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (IGNITE-6607) Thin client: protocol documentation

2018-01-18 Thread Denis Magda (JIRA)

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

Denis Magda commented on IGNITE-6607:
-

[~pgarg] , great job! I've finished with the review and did minor improvements.

 

Please announce that the doc is ready for 2.4 on the @dev list sharing all the 
links prepared.

> Thin client: protocol documentation
> ---
>
> Key: IGNITE-6607
> URL: https://issues.apache.org/jira/browse/IGNITE-6607
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 2.4
>
>
> Document thin client protocol on Apache Ignite readme.op:
> * Common message format (length, flags)
> * Data types (endianness, strings, etc)
> * Request/Response format for each message type
> * How to connect
> A list of supported commands can be taken from here:
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/platform/client/ClientMessageParser.java
> The protocol documentation format can be similar to REST API:
> https://apacheignite.readme.io/docs/rest-api



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (IGNITE-6607) Thin client: protocol documentation

2017-11-02 Thread Denis Magda (JIRA)

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

Denis Magda commented on IGNITE-6607:
-

The protocol APIs have to be documented on readme.io. Ignite wiki is good for 
implementation details.

> Thin client: protocol documentation
> ---
>
> Key: IGNITE-6607
> URL: https://issues.apache.org/jira/browse/IGNITE-6607
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.4
>
>
> Document thin client protocol on Ignite wiki: 
> https://cwiki.apache.org/confluence/display/IGNITE/Design+Documents
> * Common message format (length, flags)
> * Data types (endianness, strings, etc)
> * Request/Response format for each message type
> * How to connect



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