diff options
author | Daniel Stenberg <daniel@haxx.se> | 2000-11-12 15:14:35 +0000 |
---|---|---|
committer | Daniel Stenberg <daniel@haxx.se> | 2000-11-12 15:14:35 +0000 |
commit | 143ff23c4fecd10e5fd080983520ff4dd1dd3d25 (patch) | |
tree | 4128ca67eced4ebc2a2bd48e9d979373b3e333ae /docs | |
parent | 6195412005a6204c69f4ad0c57d191c2d8a58482 (diff) |
updated config file section
Diffstat (limited to 'docs')
-rw-r--r-- | docs/TODO | 27 |
1 files changed, 27 insertions, 0 deletions
@@ -52,6 +52,33 @@ For the future be possible to get specified *exactly* as it is done on a shell command line). + Alternatively, and preferably, we rewrite the entire config file to become + a true config file that uses its own format instead of the currently + crippled and stupid format: + + [option] = [value] + + Where [option] would be the same as the --long-option and [value] would + either be 'on/off/true/false' for booleans or a plain value for [option]s + that accept variable input (such as -d, -o, -H, -d, -F etc). + + [value] could be written as plain text, and then the initial and trailing + white spaces would be stripped off, or it can be specified within quotes + and then all white spaces within the quotes will count. + + [value] could then be made to accept some format to specify an environment + variable. I could even think of supporting + + [option] += [value] + + for appending stuff to an option. + + As has been suggested, ${name} could be used to read environment variables + and possibly other options. That could then be used instead of += operators + like: + + bar = "foo ${bar}" + * rtsp:// support -- "Real Time Streaming Protocol" (RFC 2326) * "Content-Encoding: compress/gzip/zlib" |