On Wed, 5 Jan 2005, Austin Schutz wrote: > Why not just add the functionality to Net::FTP? Or you could > subclass Net::FTP and call it something clever like Net::FTP::TLS. Because Net::FTP is written in a way that makes it extremely hard to make needed modifications. It is a very well-thought, large and organized object hierarchy. I tried adding TLS support to it almost 2years ago, contacted it's author, heard that there is large redesign coming, which will allow changes needed for encryption, however there is still no TLS in Net::FTP, and I'm sitting here on encryption-enabled client for the past two years. Do you think that I should keep it to myself for the next few years?
Additionally Net::FTP works with very large range of ftpservers, which fills code with lots and lots of special cases, this (and elaborate object hierarchy) makes it very hard for someone to come and extend it, and after trying to do that, I can only conclude that I'm too stupid to be playing with its internals. -- Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 We're giving you a new chance in life, and an opportunity to screw it up in a new, original way.