This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Steven.Hartland, loewis, vstinner
Date 2010-01-21.02:09:10
SpamBayes Score 8.101404e-05
Marked as misclassified No
Message-id <1264039752.71.0.672686679677.issue7727@psf.upfronthosting.co.za>
In-reply-to
Content
Marshaller.dump_string() encodes a byte string in <string>...</string> using the escape() function. A byte string can be encoded in base64 using <base64>...</base64>. It's described in the XML-RPC specification, but I don't know if all XML-RPC implementations do understand this type.
http://www.xmlrpc.com/spec

Should we change the default type to base64, or only fallback to base64 if the byte string cannot be encoded in XML. Test if a byte string can be encoded in XML can be slow, and set default type to base64 may cause compatibility issues :-/
History
Date User Action Args
2010-01-21 02:09:12vstinnersetrecipients: + vstinner, loewis, Steven.Hartland
2010-01-21 02:09:12vstinnersetmessageid: <1264039752.71.0.672686679677.issue7727@psf.upfronthosting.co.za>
2010-01-21 02:09:11vstinnerlinkissue7727 messages
2010-01-21 02:09:10vstinnercreate