Thats somehow a paradox question, cause XML is supposed to be a good textual format, so why don't you parse it on the "server" side?

Anyway if the other side also speaks Perl you could use Data::Dumper to serialize¹ the data (if it's purely textual)

Otherwise JSON and YAML are widespread options.

Cheers Rolf

( addicted to the Perl Programming Language)

update
¹) here a snippet from the docs:

use Data::Dumper; #... $boo = [ 1, [], "abcd", \*foo, {1 => 'a', 023 => 'b', 0x45 => 'c'}, \\"p\q\'r", $foo, $fuz]; # ... $bar = eval(Dumper($boo)); print($@) if $@; print Dumper($boo), Dumper($bar);

use $data=Dumper($boo) on sender side and $bar = eval($data) on receiver side.


In reply to Re: how to send parsed data to server by LanX
in thread how to send parsed data to server by Anonymous Monk

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.