[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-wget] [PATCH] New option: --rename-output: modify output filena
Re: [Bug-wget] [PATCH] New option: --rename-output: modify output filename with perl
Sun, 04 Aug 2013 22:52:16 +0200
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Micah Cowan <address@hidden> writes:
> On Thu, Aug 01, 2013 at 01:24:12PM +0200, Giuseppe Scrivano wrote:
>> Tim Ruehsen <address@hidden> writes:
>> > That is basically a good idea.
>> > Do you have in mind to keep as close to the standard CGI environment
>> > variables
>> > as possible ? Or do you think of the CGI environment principle ?
>> > If the latter, we should use an own namespace and let environment
>> > variables
>> > start with WGET_.
>> In any case it won't be CGI so we have the freedom to do whatever we
>> like :-)
>> I think it is good to make a difference between HTTP headers and other
>> variables, generated by wget, that we would like to pass to the external
> How would you handle FTP urls, though?
I still think the namespace approach can handle the FTP case as well.
In this case the URL would be part of the more generic WGET namespace
(WGET_URL). Whatever can be abstracted over FTP and HTTP can go in the
Probably we can have something FTP specific as well, like
FTP_PERMISSIONS (file permissions), but that can be left to the specific
protocol and I wouldn't worry much about FTP now.
Does it still sound like a reasonable idea?