Hrvoje Niksic <[EMAIL PROTECTED]> writes:
> "Dan Harkless" <[EMAIL PROTECTED]> writes:
> > I think the most straightforward mapping would also be the most attractive:
> >
> > ftp/site/dir/file
> > http/site/dir/file
>
> Don't forget the port, if you aim for completeness.
Yeah, you've probably seen the subsequent messages on this by now where we
talk about this. I do think port 80 should be implied, though, just as it
almost always is in URLs.
> > Wget should certainly have an option to make it behave this way. In
> > fact, I'd prefer it to behave that way by default, for the reasons
> > you mention, and introduce an option to leave off the protocol.
>
> That would suck for people who have come to expect the current
> behaviour.
Well, it wouldn't be very tough for them to adjust their archives by moving
the hostname directories into "ftp" or "http" directories. Or else use the
option that makes it leave off the protocol.
As long as we document the change clearly, it doesn't seem that bad to me.
To me being destructive to files when FTP and WWW servers are run on the
same machine is a worse evil than temporarily confusing some people who
don't read the documentation when upgrading to Wget 1.7 from an older
version.
> I had different thoughts: I would like have liked to not include the
> host name by default, since hosts are not traversed by default anyway.
And only create the hostname directories when -H is specified? Yuck.
---------------------------------------------------------------
Dan Harkless | To help prevent SPAM contamination,
GNU Wget co-maintainer | please do not mention this email
http://sunsite.dk/wget/ | address in Usenet posts -- thank you.
