Ok, this is a little bit gross, but it is possible to use the MIME::Base64::encode_base64() method to do the encoding, and you can specify that you don't want it to insert newlines. This works, but you have to be careful to decode the data on the other end (i.e. it doesn't happen automagically), because RPC::XML doesn't know that its payload is base64 encoded. It does know if you use the XML::RPC::base64->new() method, which wraps the data in <base64> tags). Not totally ideal, but I think I have my solution. :^)

Thanks to all for your suggestions!
-brian

In reply to Re: Re: Re: Re: Sending application-specific XML as a string paremeter to an RPC::XML method. by nenbrian
in thread Sending application-specific XML as a string paremeter to an RPC::XML method. by nenbrian

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.