[infinispan-issues] [JBoss JIRA] (ISPN-5357) Hot Rod protocol 3.0

[Galder Zamarreño (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068913#comment-13068913 ] 

Galder Zamarreño commented on ISPN-5357:
----------------------------------------

Another idea: use ping to provide some hints back to the client? E.g. if the server is configured with compatibility, the client could adjust hashing, see ISPN-5477

> Hot Rod protocol 3.0
> --------------------
>
>                 Key: ISPN-5357
>                 URL: https://issues.jboss.org/browse/ISPN-5357
>             Project: Infinispan
>          Issue Type: Enhancement
>            Reporter: Galder Zamarreño
>
> A binary protocol rethink is needed to take better advantage of CPUs and buffering. This is based on the ideas of Martin Thompson's Simple Binary Encoding [blog post|http://mechanical-sympathy.blogspot.cz/2014/05/simple-binary-encoding.html]
> In essence, we need to move Hot Rod protocol towards having mostly fixed size fields, hence getting rid of `vInt` and `vLong` formats which although safe some bytes, they hinder long stream reading patterns.
> An optional part here would be whether to consider using SBE directly, but this JIRA should be mostly oriented at making sure we have a protocol that can be read fast and efficiently.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)