Micah Cowan <[email protected]> writes: > On Thu, Aug 01, 2013 at 01:24:12PM +0200, Giuseppe Scrivano wrote: >> Tim Ruehsen <[email protected]> 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 >> process. > > 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 WGET namespace. 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? Giuseppe
