Re: WWWOFFLE Version 2.9-beta released

Andrew M. Bishop <[email protected]> wrote:
> Miernik <[email protected]> writes:
>> BTW I have wwwoffle set up this way in online mode:
>> 
>> OnlineOptions
>> {
>> <http://*/*.pdf>         request-changed         = -1
>> <http://*/*.pdf>         request-changed-once    = yes
> 
>>                          request-changed         = 0
>>                          request-changed-once    = no
>> }
> 
> The first two options in each group of four will make sure that pages
> that you don't want to be refreshed often will only be checked once
> when online and the other pages will be checked each time that they
> are requested.

I always thought that the "request-changed-once" option worked
differently (although I was not exactly sure how it works, even though I
spent many minutes reading its description, the description is not clear
and specific enough). I thought that if it is set to "yes" the page will
be fetched once per online session, but only if some other option
instucts WWWOFFLE to fetch the page from internet at all, otherwise
always use cached version. So what I wanted here for PDFs for example
is:

<http://*/*.pdf>         request-changed         = -1
<http://*/*.pdf>         request-changed-once    = no

However, isn't that equivalent to just:

<http://*/*.pdf>         request-changed         = -1

is it?
Or maybe it isn't, because the default for request-changed-once is
"yes". But then the description of request-chaged which says "Setting
this value negative will indicate that cached pages are always used
while online" is a bit misleading, because the "always" is in fact
"always, provided request-changed-once is not set to yes". And because
it is set to yes by default, the explanation sentence is by default not
true.

Anyway it is still not 100% clear for me how "request-changed-once"
works, and its description surely needs to be improved. I promise to
supply a more clear one, when I understand for sure how it works.

The clause "This option takes precedence over the request-changed
option" also does not give clarity about this, because it doesn't say
when it takes precedence: when it is set to "yes" or when it is set to
"no"? It doesn't make sense to have it take precedence over
"request-changed" in both cases, as then the request-changed option
would never affect anything.

-- 
Miernik             _________________________  xmpp:[email protected]
___________________/_______________________/      mailto:[email protected]
Protect Europe from a legal disaster. Petition against software patents
http://www.noepatents.org/index_html?LANG=en