On Tuesday, August 02, 2011 04:06:53 PM Brian Mathis wrote: > Instead of suggesting alternate technologies, Ok, so this implies that suggesting alternatives is bad... > it should be suggested > to not use an ftp client at all and instead use a scripting language, > such as perl or python, that has libraries meant for talking to these > protocols. Their man pages pretty much show you how even if you don't > know the language. Wait - isn't that an alternative technology?!? > The questionable thing is not using entrenched protocols, but using > old methods like redirecting ftp commands via STDIN into a client to > control it. /bin/sh is an "old method". TCP is pretty ancient, as well. For that matter, UNIX is REALLY ancient. Yet somehow, they are not only still useful, but highly relevant. Wheels are also old technology! There are often situations that have special needs that alternatives don't accomodate. For example, a general purpose tool (such as tcp wrappers in a scripting environment) often don't give you the fine level of control that you may need for special needs. Such as, for instance, the web-based product that adds an optional http header to indicate an error condition. Tools like wget or curl don't always allow access to the options needed to access this and so "sending stdout thru a pipe to an FTP client" might be preferable. I've been around the block long enough to know that those who are most certain they have the right answer right away are usually those least likely to have it. Science backs this conclusion up, it's called the Dunning-Kruger effect. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110802/a003a689/attachment-0004.html>