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). | [reply] |
| [reply] |
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.
| [reply] |
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.
| [reply] |
lib::http is not for remote process call, if you haven't undertand it yet! Is just a different way to USE libraries from your Perl interpreter, much more about how to distribute and update your code, than call it.
Graciliano M. P.
"Creativity is the expression of liberty".
| [reply] |