in reply to Using objects and basic types from other Perl interpreters transparently.

The main purpose of this module is to use Perl modules without need to install them, since with this resource you can use a remote object without actually have the class of this object locally. Also will be possible to make function calls that are holded remotely, actually will be possible to have a package that actually runs in other interpreter, since the main idea is to have everything transparent.

I'd just use SOAP::Lite myself.

  • Comment on Re: Using objects and basic types from other Perl interpreters transparently

Replies are listed 'Best First'.
Re: Re: Using objects and basic types from other Perl interpreters transparently.
by gmpassos (Priest) on Apr 12, 2004 at 13:13 UTC
    I didn't know SOAP::, but seems that we need to create an interface, or a service, to access that remotely.

    The idea with RPO is to write a normal code, or get an existing code, and make some part of it to work remotely.

    I know that I'm not inventing the idea, or I'm not the 1st to implement something for remote control. But, at least, I'm the 1st to implement in this architecture and with transparency use in the code.

    I will take more look in SOAP... ;-P

    Graciliano M. P.
    "Creativity is the expression of the liberty".

[reply]

      I'm the 1st to implement in this architecture and with transparency use in the code.

      Once you've set everything up and worked around its somewhat pathologic way of doing things, SOAP::Lite is fairly transparent. This is probably dangerous, as many programmers don't think of the security implications of directly executing remote methods. Many programmers have a hard enough time with the more limited CGI environment.

      ----
      : () { :|:& };:

      Note: All code is untested, unless otherwise stated

[reply]
[d/l]

In Section Meditations