[
https://issues.jboss.org/browse/TEIID-3731?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-3731.
-----------------------------------
Fix Version/s: (was: 9.0)
Resolution: Rejected
In working through the potential issues with this, I'm just going to scrap the work I
had started as part of the last round of performance testing. If we were to go down this
path, we'll probably want to just have dual schemes rather than trying to insert
custom object input/output and reusing the existing writeexternal methods.
Introduce an alternative protocol to lessen the usage of java
serialization
---------------------------------------------------------------------------
Key: TEIID-3731
URL:
https://issues.jboss.org/browse/TEIID-3731
Project: Teiid
Issue Type: Feature Request
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Even with heavy usage of externalizable there is still an overhead to java serialization
blocking and reference tracking. With custom object input/output we can eliminate the
need for java serialization with most messages.
This however would need to work beside the existing java serialization protocol for
backwards compatibility.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)