removed the config file entry as that has been much improved lately

diff --git a/docs/TODO b/docs/TODO
index 179dc40..a96d511 100644 (file)
--- a/docs/TODO
+++ b/docs/TODO
@@ -52,39 +52,6 @@ For the future
    something being worked on in this area) and perl (we have seen the first
    versions of this!) comes to mind. Python anyone?
 
- * Improve the -K config file parser (the parameter following the flag should
-   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"
 
    HTTP 1.1 clearly defines how to get and decode compressed documents. There
@@ -98,7 +65,7 @@ For the future
    sniffing. This should however be a library-based functionality. There are a
    few different efforts "out there" to make open source HTTP clients support
    this and it should be possible to take advantage of other people's hard
-   work.
+   work. http://modntlm.sourceforge.net/ is one.
 
  * RFC2617 compliance, "Digest Access Authentication"
    A valid test page seem to exist at: