|There's more than one way to do things|
Re: Blessed Objects and RPCby submersible_toaster (Chaplain)
|on Oct 02, 2003 at 04:37 UTC||Need Help??|
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