[teiid-issues] [JBoss JIRA] (TEIID-3731) Introduce an alternative protocol to lessen the usage of java serialization
[
https://issues.jboss.org/browse/TEIID-3731?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3731:
---------------------------------------
There are several reasons.
The first is that whatever is missing is quite a lot of stuff. Standard logic would need
remapped (especially around cursoring, sessioning, and exception handling), streaming
hasn't been implemented, type handling would need to be expanded, the teiid JDBC
extensions would need reimplemented - and the asynch stuff does not fit well. And of
course we still would be providing our own JDBC client so it's not like we would own
significantly less code.
The other reason is that we'll still need to provide a backwards compatible transport
for the whole release, so we'd continue to have all the existing messaging classes as
well.
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
Fix For: 9.0
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)