From 70ce1cda1f691b447eb2262e007ccb52460e628e Mon Sep 17 00:00:00 2001 From: Robert James Kaes Date: Thu, 25 Oct 2001 16:16:32 +0000 Subject: Moving the TODO list from the doc directory to the root directory so that it's more visible. --- TODO | 43 +++++++++++++++++++++++++++++++++++++++++++ doc/TODO | 43 ------------------------------------------- 2 files changed, 43 insertions(+), 43 deletions(-) create mode 100644 TODO delete mode 100644 doc/TODO diff --git a/TODO b/TODO new file mode 100644 index 0000000..5d3a526 --- /dev/null +++ b/TODO @@ -0,0 +1,43 @@ +TODO List +--------- + +The following are features that I would like to add to tinyproxy in the +future. Where possible, I've listed the person who suggested it. This +list is in no particular order. And hey, if you want to implement one of +these, or another idea you have, go right ahead. Just mail me the diff +against the current tree and I'll integrate it if possible. + + [ Actually, the ordering has become kind of important as of + late. Basically, I'm adding new ideas to the bottom of the list + as I go. ] + + * Include hooks so other types of proxies can be modularly added to + the source tree. Then people can simply choose which types of + proxies (ftp, www, etc) they'd like enabled in tinyproxy.h + Suggested: Tarun Tuli. + + * Find a more elegant solution to embedding HTML documents in the + source than the current method. (see httperr() and showstats() for + examples of how it's done right now). + + * Include a function to rewrite the incoming requests. Should not be + much of a problem. Just need to modify the process_method() code + to look up the URL and rewrite it. If we want to go really fancy + with RegEx mapping this could get ugly. :) + + * Have the ability to send the data from the connections through an + external filtering program. I kind of like this idea, but I don't + really have a good way of doing it yet. + Suggested: Ed Avis + + * Include the ability to rewrite both incoming and outgoing headers. + + * Enable an option for chroot() jailing tinyproxy. + + * Add an option which allows the blocking of connections to certain + ports (like 25, 110, etc.) that might be used for "bad" things. :) + + * Come up with a more consistent (and elegant) way of logging errors + for the administrators. Right now it's more a hodge-podge + collections of error messages without a _real_ standard. I would + prefer a more uniform look. \ No newline at end of file diff --git a/doc/TODO b/doc/TODO deleted file mode 100644 index 5d3a526..0000000 --- a/doc/TODO +++ /dev/null @@ -1,43 +0,0 @@ -TODO List ---------- - -The following are features that I would like to add to tinyproxy in the -future. Where possible, I've listed the person who suggested it. This -list is in no particular order. And hey, if you want to implement one of -these, or another idea you have, go right ahead. Just mail me the diff -against the current tree and I'll integrate it if possible. - - [ Actually, the ordering has become kind of important as of - late. Basically, I'm adding new ideas to the bottom of the list - as I go. ] - - * Include hooks so other types of proxies can be modularly added to - the source tree. Then people can simply choose which types of - proxies (ftp, www, etc) they'd like enabled in tinyproxy.h - Suggested: Tarun Tuli. - - * Find a more elegant solution to embedding HTML documents in the - source than the current method. (see httperr() and showstats() for - examples of how it's done right now). - - * Include a function to rewrite the incoming requests. Should not be - much of a problem. Just need to modify the process_method() code - to look up the URL and rewrite it. If we want to go really fancy - with RegEx mapping this could get ugly. :) - - * Have the ability to send the data from the connections through an - external filtering program. I kind of like this idea, but I don't - really have a good way of doing it yet. - Suggested: Ed Avis - - * Include the ability to rewrite both incoming and outgoing headers. - - * Enable an option for chroot() jailing tinyproxy. - - * Add an option which allows the blocking of connections to certain - ports (like 25, 110, etc.) that might be used for "bad" things. :) - - * Come up with a more consistent (and elegant) way of logging errors - for the administrators. Right now it's more a hodge-podge - collections of error messages without a _real_ standard. I would - prefer a more uniform look. \ No newline at end of file -- cgit v1.2.3