[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1090) Hot Rod protocol improvements for version 2

Galder Zamarreño (JIRA) jira-events at lists.jboss.org
Tue May 17 06:01:01 EDT 2011


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

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

Well, once you get a SuspectException, if you want to retrieve the address you'd do getAddress(), so it's an addition to the API to be specific. This would also need a new constructor to take the message + address.

> Hot Rod protocol improvements for version 2
> -------------------------------------------
>
>                 Key: ISPN-1090
>                 URL: https://issues.jboss.org/browse/ISPN-1090
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Cache Server
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 5.1.0.BETA1, 5.1.0.Final
>
>
> This JIRA will act as a place to keep track of enhancements to the Hot Rod protocol that should be included in version 2 of the protocol:
> - We need a new error status code so that clients can detect when a node has been suspected and so react accordingly (i.e. not bubble it up but instead failover). Currently, this can be solved by checking whether the error message contains SuspectException but this is not nice.
> - Since we're not gonna be supporting asymmetric clusters in the mean time, we need a new error status code to deal with situations where the cache is not defined in the server. Currently we check for CacheNotFoundException in the message but that's not nice.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the infinispan-issues mailing list