You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by R J Scheuerle Jr <sc...@us.ibm.com> on 2002/02/11 20:00:18 UTC
Multi-Ref vs. Single Ref
Axis Multi-Ref serialization assumes that all primitives (and arrays)
are multi-ref'd.
* More text is passed over the wire.
* Deserializer must do more work to unmarshal data.
* Multi-ref not supported by some services.
Axis Single-Ref serialization assumes that nothing can be multi-ref'd:
* This is wrong in some cases and can lead to problems.
So is there a way to do the following....
1) Start the soap serialization process using the "single ref" approach
but with the capability to detect "multi-refs".
2) If an object is encountered that is multi-ref'd, stop serializing
and
revert back to the beginning and re-serialize using the
"multi-ref" approach.
This has the following advantages.
a) messages that don't have mult-references are transmitted in an
optimal manner
without any additional performance overhead.
b) messages that do have multi-references at most incur the overhead of
an
additional pass over the data.
c) few changes would be needed to the present code (?)
Comments? Can anyone give me some insight as to how one could "rewind"
to the beginning of serialization.
Thanks,
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)