in reply to ftp scripts
It's certainly possible to roll your own code for an ftp client, but given the complexity of the task and the learning curve of getting it right, why? There are a plethora of modules available on CPAN for almost any situation in the ftp client arena.
What do you have against using modules?
If you really want to do it yourself, you're going to have to start reading the ftp rfcs, and work with raw sockets, I think.
Re^2: ftp scripts
by darrengan (Sexton) on Aug 26, 2005 at 07:16 UTC
|
Hie hubb0r,
does all this modules comes with perl by default? (sorry, i am totally new to perl, i am a ASP guy trying to learn perl).
i am working on a huge production server which i can't just simply install a new module.
thats why i need to have some raw scripts..
Thanks for sharing with me...
Cheers,
Darren
Florist In Malaysia | [reply] |
|
perldoc Net:::FTP
Failing that, make friends with an admin. :)
| [reply] [d/l] |
|
If you can install a new script, you should be able to install most modules too.
Anyway, Net::FTP is not part of the perl core distribution, but its libnet package is so useful that it's practically always available on machines with a perl install anyway. At the very least, it should be available as a system package (rpm, deb, ppm, whatever) for any system you'd want to run a production server on.
| [reply] |
|
Keep in mind that modules don't have to be installed system-wide; you can install a private copy of Net::FTP in a private directory, and put use lib '/path/to/private/dir'; at the top of your script to use it.
| [reply] [d/l] |
|