Hi Andrew,

I've made a list of suggestions to make wwwoffle handling easier:

1. When I edit wwwoffle options and press "update", I subsequently need to 
press "config" to make changes take effect. It would be easier if "config" is 
run each time "update" is clicked.
BTW, what is the "config" button at the end of the page for? Don't I have to 
run "update" first?

2. When deleting pages from a cache, it would be more convenient if the 
updated index is shown right after clicking "delete".

3. purge: max-size=0 means that there is no limit. However, I'd expect that 0 
means that the cache is empty after purging. I'd find the former more 
intuitive in the form max-size=infinite or -1. Also, a user may want to 
completely empty the cache, which I do till now by cd <cache>, rm -r *.

4. the offline-rerequest problem: I suggest to introduce an option such as 
"rerequest-cached-pages = yes|no" to replace "pragma-no-cache" and 
"cache-control-no-cache". Unless there's a need to treat the latter two 
options separately, it's easier to deal with just one (self-explaining) 
option to fix rerequesting problems.

5. The examples for Censor Header are unclear:
### Example ###
# Don't send the username.
# From = yes
What does this mean? From=yes makes wwwoffle not send the username?

Also, there should be a description for what happens to cookies, e.g. if 
cookies are enables by wwwoffle but not by the browser.

6. If I enter sites to be fetched with http://localhost:8080/refresh-options/ 
and push "fetch now", wwwoffle doesn't tell when fetching is over (as it does 
for wwwoffle -fetch).

7. wwwoffle should go online before fetching if it is offline.

8. The wwwoffled.rc script in /contrib/redhat2 is not easy to find and people 
probably don't know where to put it and what links to create for sys v init. 
Some pointers in the faq would be helpful.

Ok, that's it for now :-) 

So long,

Boris



Reply via email to