Update: I should be shot for reading FUD on the web instead of knuckling down and examining POD and modules. perrin's point is well taken , SOAP is slow. For the purposes of my current design this could be a problem. Thanking you all for sharing virtue and excersising patience.

Thanking Zaxo, I will endevour to explain myself better. I anticipate problems with this idea, please pick holes in it.

To pass blessed objects between two remote perl processes, the sender (given a blessed object) determines what package it has been blessed into, and sends the package name and the serialized data via some transport (like SOAP or XML-RPC) that copes nicely with strings, calling the remote method 'rebless'

The recieving side receives the SOAP data, calls the rebless method passing the two arguments. Rebless would de-serialize the data, and bless it into the named package.

Of course this sort of thing has major limitations , like the consistancy of packages being installed or at the correct version. File handles are another one that would break if passed in this way

I realise now, just how many things I've overlooked. Damn. I guess its time to change design.


I can't believe it's not psellchecked

In reply to Re: Blessed Objects and RPC by submersible_toaster
in thread Blessed Objects and RPC by submersible_toaster

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.