Re: lynx-dev Re: lynx timeline

[Leonid Pauzner]

4-Jun-2003 13:43 Ilya Zakharevich wrote:
> On Tue, Jun 03, 2003 at 03:42:06PM -0700, Ilya Zakharevich wrote:
>>   d) no-cache should be ignorable per lynx.cfg;
>>
>>   e) expiration date should be ignorable (best in two steps: I should
>>      be able to request "no expiration in less than 6 min", AND I
>>      should be able to request "ask-with-default-no for expiration
>>      dates below 1.5 hour").
>>
>>   f) If a document is in the cache (or the rendering is in memory), on
>>      reload it should not be cleared from the cache until the
>>      connection to the server is opened; if the connection fails, the
>>      user should have a choice to reuse the old version;

I read the code yesterday. It looks like no_cache code in lynx is rather
weird, it should be completely rewritten which is not acceptable before the
release. Will see if it could be "fixed" safely.

> Leonid asks for names for .cfg entries.

> d) HONOR_NO_CACHE=yes/no

"no_cache" is effectively the same as "expire <= now"
it will acts differently according to your suggestions d) and e).

> e) NO_EXPIRATION_BEFORE=seconds1
>    ASKNO_FOR_EXPIRATION_BEFORE=seconds2
>    ASKYES_FOR_EXPIRATION_BEFORE=seconds3

>    gives 4 intervals for age of expired documents:

>       0..seconds1        -    silently ignore expiration
>       seconds1..seconds2 -    ask user about reload with default=no
>       seconds2..seconds3 -    ask user about reload with default=yes
>       seconds3..Inf      -    silently reload

And we will be biased between the client clock and the server clock...

> f) "Connection failed (reason); use previous version ([yes]/no): "

> Thanks,
> Ilya

> ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden



; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden