On Thu, August 25, 2005 11:47 am, Christopher Sawtell said: > On Thu, 25 Aug 2005 10:49, Steve Holdoway wrote: >> On Thu, August 25, 2005 10:39 am, Christopher Sawtell said: >> > On Thu, 25 Aug 2005 10:24, Steve Holdoway wrote: >> >> On Thu, August 25, 2005 10:17 am, Christopher Sawtell said: >> >> >> If it's a bug, then how are you going to implement a standard file >> >> >> naming >> >> >> scheme across http and ftp? >> >> > >> >> > if there is a line such as this:- >> >> > Content-disposition: filename=laby_1.0.1.tar.gz >> >> > in the http headers then use the filename mentioned. >> >> > otherwise use the name of the file on server as is done currently. >> >> > >> >> > I have not yet examined the wget code so cannot comment on the >> exact >> >> > details. >> >> > >> >> > -- >> >> > CS >> >> >> >> Once again, how are you going to do this in ftp, where there are *no* >> >> headers? >> > >> > Once again:- >> > "use the name of the file on server as is done currently." >> > >> >> I'm quite happy to lobby for an extra switch to enable this >> >> functionality >> >> for http gets, but not as a default. >> > >> > Why, what is the problem? > Note that the No. 1 entry in the current ( wget-1.10 ) TODO file says > this:- > > <quote type='precise'> > * Honor `Content-Disposition: XXX; filename="FILE"' when creating the > file name. If possible, try not to break `-nc' and friends when > doing that. > </quote> > >> so you think it's acceptable behaviour for the web designer to create >> his >> directory hierarchy on your pc *without* you asking him to do so? > No, & my suggestion does not do that. > >> and it's ok to get foobar.exe when you ask for something else? > I think it is perfectly ok to ask for a file by a reference to it rather > than > by it's actual filename. Well, we'll have to disagree there. > >> wget's main function is to be used in scripting, as in Nick's original >> example ( see the first para of the intro on the gnu website ). How are >> you going to process any returned files when you a) don't know their >> name >> and b) don't know where they are? > I have no problems with being able to construct script phrases such as:- > > for n in 1 2 3 4 5 > do > wget http://file_archive_site.tld/get-file.php?file_id=$n > done > > You cannot do that at the moment, but I can see that it could be very > useful.
Yes you can, and get an uniquely named and known file every time. But what if one of the above archives is updated from .01 to .02? How do you automatically post process it? You're missing the point by assuming the links to be static. Scripts that use this sort of idea will break every time the link is updated. And it will be as websites are developed and software packages are updated. > >> Things like that are problems. Big ones. > If that really is the case please please could you make your concerns > known to > the wget team. No they're *your* concerns. *I* don't want any changes. > > To post to the list, send mail to <[email protected]>. To > subscribe, send mail to <[EMAIL PROTECTED]>. > > -- > CS > I'm bowing out of this thread. I've stated my views, and the thinking behind it. Feel free to disagree. Steve -- Windows: Where do you want to go today? MacOS: Where do you want to be tomorrow? Linux: Are you coming or what?
