If you want to execute the code that exists on the other machine, consider SOAP. Briefly, SOAP is a remote procedure call (RPC) mechanism that serializes your function call and sends it over the net. It is language independent. It uses XML to specify the data (args and return) and usually HTTP to make the data transfer. You don't need to know XML to use it. There is a perl module SOAP::Lite to make it easy along with lots of other SOAP modules.
HTH, --traveler
| [reply] |
Well, what's your goal? Do you want to just execute this code (in which case, just copy it your machine and run it) or do you want to execute it on the other machine? If it's the latter, NFS won't do it. CGI was a very good idea, but failing that you can use one of the other RPC mechanisms for Perl, like PlRPC. | [reply] |
In addition to SOAP and RPC, you could always use CORBA to run the object on the other machine. Check out the ORB package for more details. Given the complexity of CORBA, I would tend to avoid it unless it's a company standard or you have CORBA resources in house. | [reply] |
I've had good success with the COPE language binding, however you'll still need an ORB to go with it, for instance ORBacus, which is free for non-commercial use, but requires a license for use in a business. I'd say use CORBA if you require a significant amount of interaction with the remote object. That is, if you're doing more than just firing it up and letting it go. CORBA is much too heavyweight otherwise.
| [reply] |