[
https://issues.jboss.org/browse/ISPN-1090?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1090:
----------------------------------------
Well, for an L1 in clients you need listeners so that you can be notified when things
change on the server side. I think this is important, particularly cos a lot of people
using Coherence like the L1 capabilities that they bring. Anyway, the L1 and event
listeners is already covered in a separate JIRA. This jira is more geared towards having:
- Small improvements that do not need a separate jira
- Link to bigger jiras such as ISPN-484 or ISPN-374.
The custom commands could be interesting but I'd like to see concrete use cases for
this.
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