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

[ https://issues.jboss.org/browse/ISPN-1090?page=com.atlassian.jira.plugin.... ] Galder Zamarreño edited comment on ISPN-1090 at 5/15/11 11:37 AM: ------------------------------------------------------------------ Another interesting idea: - It'd be interesting for error messages to have 0-n parameters sent back to the client. This way, you could formalize suspect exceptions being thrown back to the client in such way that servers could tell clients in a more explicit way which node was suspected and so they could avoid trying to failover to that node if their topology view has not been updated. At the moment there's no formalization of this, so to implement this would require clients parsing the error message in a particular way to derive this information, and relying on this is too brittle. Note: In the case of SuspectException, to make this more reliable, it would require that an API change is done so that it includes a member instance variable. This is probably something worth doing now, just before 5.0 release. I'll create a separate jira for this. was (Author: galder.zamarreno): Another interesting idea: - It'd be interesting for error messages to have 0-n parameters sent back to the client. This way, you could formalize suspect exceptions being thrown back to the client in such way that servers could tell clients in a more explicit way which node was suspected and so they could avoid trying to failover to that node if their topology view has not been updated. At the moment there's no formalization of this, so to implement this would require clients parsing the error message in a particular way to derive this information, and relying on this is too brittle. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira