[
http://jira.jboss.com/jira/browse/JBCACHE-752?page=comments#action_12343243 ]
Manik Surtani commented on JBCACHE-752:
---------------------------------------
See JBCACHE-766.
Some methods - put(fqn, key, value) and remove(fqn, key) - return the old value of the
attribute. Thi sreturn value is only used in the "local" version of the method.
The return value is not used in "remote" versions.
Returning nulls for these (if remote) will simplify classloading and improve marshalling
(of return values) performance, and reduce network traffic.
Look into using JBC Marshaller implementations for responses as well
as requests
--------------------------------------------------------------------------------
Key: JBCACHE-752
URL:
http://jira.jboss.com/jira/browse/JBCACHE-752
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Replication
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 2.0.0
In JGroups 2.4 the ability to use a Marshaller for responses as well as requests was
added. At some point JGroups may require that the *same* marshaller instance handle both.
JBC's current marshallers can't do this; need to look into what it would take to
do it.
Should be simple, as RPC responses in JBC are either null, an exception, or a byte[] (for
RPC based state transfer).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira