The main reason for saving LibXML instances is that I want to save XML parsing time.

That statement is nonsense. Like I said earlier, the objects need to be serialised no matter what. What reason do you have to believe that serialising to XML would be slower to serialising to whatever you can come up with? Given that XML is very easy to generate and parse, and given that LibXML is a *very* fast parser, serialising to XML might actually be faster! In fact, considering it has direct access to the underlying objects, I'd bet it runs circles around your serialiser and parser. Come back when you have benchmarks.

In reply to Re^3: Saving XS-objects to memcached by ikegami
in thread Saving XS-objects to memcached by KSURi

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.