James G. Sack (jim) wrote:
Ralph Shumaker wrote:
Michael O'Keefe wrote:
Ralph Shumaker wrote:
..
I'm not sure what you mean by "If it failed one way, it would try
another" ? Do you mean it would look up a listing somewhere and try
another cache location ?
Well, this memory has become a little cloudy. I remember reading about
it in the documentation for FileHound. And I remember seeing in its
status window saying something like ~"couldn't do this, trying this
instead..."~. One of the things was different ports IIRC. For some
reason I'm thinking that most of the trying different things had to do
with ftp downloads, because of various options which may or may not work
in different cases...
Guessing that might have been "trying passive mode" (or some such message).
That rings a bell vaguely, so, maybe.
I suppose "different ports", might have meant http->https, ftp -> ftps?
Possibly, tho I seem to recall that http uses port 80 and ftp uses
something else. But even http and ftp have alternate ports that they
can sometimes use, right? For some reason, I'm thinking it was more
this than what you said. Or maybe this is just semantics (i.e. 80 =
http, ??? = https, etc.). But what I seem to recall is that FileHound
would try different port numbers. In fact, it may even have tried the
ftp port number automatically instead of the http port number, even when
you fed it an http URL. (Certainty of recollection on this point is
somewhat slim.)
I certainly miss that program.
--
Ralph
--------------------
Introducing ambiguity is bad.
--Stewart Stremler
Give me ambiguity, or give me something else!
--kelsey hudson
--
KPLUG-Newbie@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
