If you look into the
get routine in FTP.pm, you'll see that it's reading a buffer, then writing it to the passed-in filehandle. If you just want to hack on it, make your own copy and save the buffer in the *ftp object and return that. Or, to be closer to "production", inherit FTP into a wrapper object and override get().
In the end, it's probably easier to write to a temporary file and parse that. The time to write and read the local file will almost certainly be a tiny fraction of the ftp connect and transmit time.
(
update) If you really want to get into it, you could look at
Net::FTPServer.  That lets you write your own site commands.  You could do "
SITE PARSE filename" and let the server parse the file and send back a 200 response with the needed data.  Now,
that would
be an efficiency!
 
p
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.