You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-dev@ws.apache.org by bu...@apache.org on 2002/12/10 05:32:25 UTC
DO NOT REPLY [Bug 15216] New: -
de/serialization independence
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15216>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15216
de/serialization independence
Summary: de/serialization independence
Product: XML-RPC
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: Source
AssignedTo: rpc-dev@xml.apache.org
ReportedBy: reed.esau@pobox.com
For serialization (object->XML) can XmlWriter be made public?
For deserialization (XML->object) can the ContentHandler be separated from
XmlRpc, allowing it to be used as an independent SAX handler, with no thread or
SaxDriver discovery code inside? Support for SAX2 DefaultHandler would be nice
too, but not critical.
Use case: where XML-RPC is being used with an alternative transport (JXTA
pipes, e.g.) this separation would allow for much cleaner client
implementations, where these modules can be used for preparing requests and
parsing responses.
Much appreciated!
Reed Esau, reed.esau@pobox.com
http://xmlrpc.jxta.org