in reply to Perl as bloatware

I don't really know exactly what you're driving at here, except maybe that NET::FTP and LWP both allow you to make FTP requests, but not with the same underlying code. It seems pretty obvious to me. When you're using LWP, your FTP request is usually made through a HTTP::Request which fits the design for how to use the module consistently across several services.
As far as a "command TCP/IP" library, I must confess to not having any idea what you're talking about. Do you want a library where we can $tcpPacket->setSYNFlag();, or are you talking something a little more high level?

Guildenstern
Negaterd character class uber alles!

Replies are listed 'Best First'.
RE: (Guildenstern) RE: Perl as bloatware
by merlyn (Sage) on Oct 09, 2000 at 18:43 UTC
    Actually, you'll find that if handed an ftp://... URL, LWP does use Net::FTP underneath! I didn't even think of that when I made my other reply, because I thought it well known that one uses the other. I was thinking of the attempt to overlap "talking on a socket" which is very different between HTTP and FTP.

    -- Randal L. Schwartz, Perl hacker

[reply]

In Section Seekers of Perl Wisdom