[
http://jira.jboss.com/jira/browse/JGRP-753?page=comments#action_12412587 ]
Bela Ban commented on JGRP-753:
-------------------------------
Sorry, I won't change this, for my arguments put forth above. This would be a change
that introduces overhead to each message for a very special case in your application.
You can generate the object the first time you de-serialize, attach it to an
application-provided header and then fetch it from that header, if you need to prevent
duplicate de-serialization.
cache object returned from Message.getObject() (deserialization
occurs on every call)
-------------------------------------------------------------------------------------
Key: JGRP-753
URL:
http://jira.jboss.com/jira/browse/JGRP-753
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.6.2
Reporter: Michael Newcomb
Assigned To: Bela Ban
Fix For: 2.6.3, 2.7
Proposed solution:
33 /** The payload */
34 private byte[] buf=null;
34.1 private Object obj;
291 final public Object getObject() {
291.1 if (obj == null) {
292 try {
293 obj = Util.objectFromByteBuffer(buf, offset, length);
294 }
295 catch(Exception ex) {
296 throw new IllegalArgumentException(ex);
297 }
297.1 }
297.2 return obj;
298 }
--
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