I think you might be missing the point. How does SOAP or XML-RPC let you load libraries across the network (NOT run code remotely)? It seems the main point of lib::http would be to make it easy to update many, many servers with new versions of modules (like gmpassos described).

Comment on Re^2: lib::http - Using virtually a Perl library from the Internet with the HTTP protocol.

So, my applications that are distributed across a bazillion servers are completely dependent on one application on one machine being up and running and not in an endless loop and ...

What's wrong with CPAN? crontab and CPAN work just fine, especially with a local CPAN repository.

Being right, does not endow the right to be rude; politeness costs nothing.Being unknowing, is not the same as being stupid.Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

TIMTOWTDI - if you don't want to update to the latest versions of CPAN modules as they're released (which you usually don't on a production system), you'd have to setup your own CPAN repository with the versions you want, and point all your servers at that.

Seems like it might be easier just to use lib::http, and install the versions you want on your central repository.

I'm not saying there's anything wrong with CPAN and cron, and I'm not defending gmpassos' method as a good one, I was just pointing out that I didn't think you initially understood the point of the module.