[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev cache control
From: |
Philip Webb |
Subject: |
Re: lynx-dev cache control |
Date: |
Mon, 13 Sep 1999 03:43:58 -0400 (EDT) |
990912 Klaus Weide wrote:
> On Sun, 12 Sep 1999, Philip Webb wrote:
>> certainly enough comment (smile), but no pointers/suggestions AFAIK ...
> I gave you a (not very precise) pointer to previous discussion
i assumed that was merely the kind of meta-discussion we're having
a/a examining actual options for changing source code.
> and an implied pointer to look for "no_cache" (or no-cache or nocache)
> in the source...
your implications are too subtle for me ... (smile)
>> i'm not interested in expiry dates etc etc,
>> simply in getting the news stories which the WP/other sites list:
> when you follow a link you don't necessarily know
> whether what lynx displays is what they send now
> or what they sent at some point earlier since starting Lynx.
news stories at WP, FT or other journals i read are new daily
or at least i know when i saw them in yesterday's listing;
they don't revise a story listed under the same title.
this is also true of most ordinary info-sites;
people who buy things or check stock prices using Lynx
will probably set CACHE_ALL_DOCUMENTS:NO in lynx.cfg .
> Some people leave Lynx running for days or weeks,
> I don't know what is your typical usage pattern.
until the rubber-band or shoe-string breaks & CHASS crashes,
ie days or weeks ...
>> all that takes is the binary flag above:
>> I (emphatic) want to tell Lynx to cache ALL documents it receives
>> -- i set the limit at 20 -- , regardless of what anyone out there says,
>> leaving me the option of ^r if i want to get a fresh copy.
> Even if it is a POST form submission, local directory listing
> or some internally generated page?
yes, yes & probably -- given that i can get a fresh copy using ^r -- :
internal pages are a possible exception, but not a big issue.
>> that should be real easy & something many real-life users would prefer,
>> so any pointers/suggestions (smile)?
> You didn't say you were ready to dive into the code,
> so my suggestion is to ask for more specific pointers then.
fine: i've archived your long explication under `lynx-todo'.
if/when i examine Lynx source, i'm probably going to need >= 1 mth
to get a proper picture of how things work, but it wb a good exercise.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb : address@hidden
ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies
TRANSIT `-O----------O---' University of Toronto
- Re: lynx-dev Keeping browsers from caching, (continued)
- Re: lynx-dev Keeping browsers from caching, David Woolley, 1999/09/10
- Re: lynx-dev Keeping browsers from caching, Philip Webb, 1999/09/10
- Re: lynx-dev Keeping browsers from caching, Klaus Weide, 1999/09/10
- Re: lynx-dev Keeping browsers from caching, Philip Webb, 1999/09/10
- lynx-dev cache control (was: Keeping browsers from caching), Klaus Weide, 1999/09/11
- Re: lynx-dev cache control, Philip Webb, 1999/09/12
- Re: lynx-dev cache control, Vlad Harchev, 1999/09/12
- Re: lynx-dev cache control, Klaus Weide, 1999/09/12
- Re: lynx-dev cache control, David Woolley, 1999/09/12
- Re: lynx-dev cache control, Klaus Weide, 1999/09/12
- Re: lynx-dev cache control,
Philip Webb <=
- expires (was: lynx-dev cache control), Webmaster Jim, 1999/09/12
- Re: expires (was: lynx-dev cache control), Klaus Weide, 1999/09/12
- Re: expires (was: lynx-dev cache control), Webmaster Jim, 1999/09/12
- Re: expires (was: lynx-dev cache control), Klaus Weide, 1999/09/12
- Re: expires (was: lynx-dev cache control), Webmaster Jim, 1999/09/12
- Re: expires (was: lynx-dev cache control), David Woolley, 1999/09/12
- Re: lynx-dev Keeping browsers from caching, Thomas Gandy, 1999/09/11
- Re: lynx-dev Keeping browsers from caching, David Woolley, 1999/09/12
Re: lynx-dev Keeping browsers from caching, Henry Nelson, 1999/09/13