A note to my previous posting (i've already anhiliated it, sorry for the new posting).
It's not really a problem for me. I just can't withstand to add a comment....
I'm aware that you, Andrew, designed wwwoffle as a 'core' server application.
However, I installed wwwooffle for some people for desktop desktop browsing.
Especially on laptops it's very useful.
To me it seems the straight (and better) solution to what browser caches try to cover.
Overkill, at first sight. But not necessarily, if it's userfriendly and scalable to desktop needs.
Now, the topic: I think I misunderstood 'purged (10 days) ' too easily.
And i'm sure I'll have to explain it to nearly all my supported clients some day.
I most probably would not have run into this if the wording would be something like:
'not purged' .......... still expiring but not yet reached the limit
'purged' .............. expired and deleted
'protected' or 'hold' ...... for age = -1
And i think a clean column output (with header) would make it even more clearer,
regardless the redundancy.


I imagine an output like ....
<<
Not Purged http://www.ibm.com ; 50 kB
Purged (10 days) http://www-307.ibm.com ; empty ( 137 kB del)
Purged (90 days) http://www.ffis.de ; 13 kB
Purged (90 days) http://wwwdb.europarl.eu.int ; 145 kB
Purged (1 days) http://www.edu.yorku.ca:8080 ; 46 kB (ok, this is just a joke ;-)
>>


... would become:

<<
status URL cache deleted time left limit
========================================================================
HOLD http://www.ibm.com 50 kB --- 00 -1
purged http://www-307.ibm.com --- 137 kB --- default
not purged http://www.ffis.de 13 kB --- 90 d 90 d
not purged http://wwwdb.europarl.eu.int 145 kB --- 5 d 90 d
>>


Probably there should be a delimiter for postprocessing (eg. sorting) the content, a tab or sth.

(hmm....this is probably an example for the law that the length of a posting is negative proportional to its importance -;)


-- mi.







Reply via email to