Actually, it's pretty much exactly like that :-) ... the only thing here is trying to match what XBeans is doing in terms of how data is transferred around.

And to answer someone else as pointed out in this thread, yes, XML would seem to be inefficient, but a hidden advantage of using XML as transfer mechanisms would be that beads would not necessarily have to lie on the same computer; the bead could easily be a report server that does something with XML and return XML back, or could be a client bead talking to a server bead, etc. In addition, beads would not necessary need to talk to other beads; using XML allows anything to be inserted into the mechanism as long as it understands the XML. Using perl internals would be nice, but at some point if you cross the machine boundary, you need to serialize the objects, and XML is a very convinent way to do this.

-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain
It's not what you know, but knowing how to find it if you don't know that's important

In reply to Re: Re (tilly) 3: Potental project - Perl Beads? by Masem
in thread Potential project - Perl Beads? by Masem

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.