[
http://jira.jboss.com/jira/browse/JBWS-926?page=comments#action_12383940 ]
Levi Purvis commented on JBWS-926:
----------------------------------
Consider just supporting XML Fast InfoSet as your binary optimization. It will then still
interoperate with other servers (Sun, Microsoft) and still be highly optimized. My tests
with Sun's JAXB/JAXWS stack shows that using Fast InfoSet performed very close to RMI
(with out taking any effort to optimize).
Why reinvent the wheel when you can use a standard with a quality parser / serializer that
is already available? The Fast InfoSet API conforms to the three standard XML API's,
so it should be easy to plug in.
https://fi.dev.java.net/
JBoss to JBoss binary optimiztion
---------------------------------
Key: JBWS-926
URL:
http://jira.jboss.com/jira/browse/JBWS-926
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-jaxws
Reporter: Thomas Diesler
Fix For: jbossws-2.1.1
With WS the client and server are fundamentally disconnected and exchange XML documents
that are valid in the context of the abstract contract defined in WSDL. Having said that,
client/server implementations might not care about the abstract contract as long as there
are no handlers involved that work on the SAAJ/DOM API. Currently all transport concerns
are delegated to jboss-remoting. It would therefore be possible to implement a binary
transfer of the SOAPMessage that is linked to a remoting protocol other than HTTP.
--
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