I actually implemented an even more robust version than that one (based
on it) -- but it is a good example. However, I can't help but wonder if
the POE modules wouldn't be a better approach now that its out there.
-Steve
On Thursday, March 20, 2003, at 04:46 PM, [EMAIL PROTECTED] wrote:
Ch
Chapter 13 of O'Reilly's "Advanced Perl Programming" has a great discussion
of, and example code for implementing RPC in perl. It's missing a few
things (encryption was the first thing I noticed), but is an excellent
starting point if you choose to follow the RPC path.
Steve
> Really, you wa
On Thursday, March 20, 2003, at 04:40 PM, [EMAIL PROTECTED] wrote:
The other reason is security (yes, I realise it does not make much
difference), but at least I would not be handing the source of my
libraries over to the purchaser of my software...
Actually, you would be handing the source ov
In a message dated 20/03/2003 16:54:04 GMT Standard Time, [EMAIL PROTECTED] writes:
Yes and no. Or maybe no and yes. Or maybe just no. As was noted on the
previous, a URL won't work out of the box. You could roll your own
quick-and-dirty using LWP and the 'eval' function. If the module were
availa
[EMAIL PROTECTED] wrote:
> Is it possible to use the require command from a perl script on one
> server, to access a library located on a different server??
> For example:
> require "http://www.dokos-gr.net/RWAPSoft/cgi-bin/my_lib.pl";
Yes and no. Or maybe no and yes. Or
