[infinispan-issues] [JBoss JIRA] Commented: (ISPN-437) Hotrod server optimisation: use SKIP_REMOTE_LOOKUP if no return values are needed

[Galder Zamarreno (JIRA)]

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

Galder Zamarreno commented on ISPN-437:
---------------------------------------

In commands where returns are simply used to decide whether to return previous value, this is fine, i.e. put or clear commands. However, in commands where I use previous value to detect whether the operation worked fine, this is risky. Particularly taking in account that if SKIP_REMOTE_LOOKUP is true or unsafe returns are configured, then conditional commands only force a remote get if the execution is transactional. Since I don't use transactions in Hot Rod, this means that if either of the two options where in use, my conditional commands could not work as reliably.

> Hotrod server optimisation: use SKIP_REMOTE_LOOKUP if no return values are needed
> ---------------------------------------------------------------------------------
>
>                 Key: ISPN-437
>                 URL: https://jira.jboss.org/browse/ISPN-437
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Cache Server
>            Reporter: Mircea Markus
>            Assignee: Galder Zamarreno
>             Fix For: 4.1.0.CR1
>
>
> it would be a good optimisation for the HR server to use SKIP_REMOTE_LOOKUP flag on put/remove/replace if I don't pass an force return value to HR server

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira