|
|
On 2009-06-25, Eirik Byrkjeflot Anonsen <eirik@xxxxxxxxx> wrote:
> Felix Karpfen <felixk@xxxxxxxxxxxxx> writes:
>
>> I am preparing for a plunge from "dial up" to "broadband" and am
>> getting ready for unforeseen side-effects.
>
> In this regard, I'd expect very little side effects, as opera most
> likely doesn't care about the sort of connection you have when it
> decides whether to reload from the net :)
>
This is not the case - see below.
>> I was hoping that someone at Opera reads the queries that are posted to
>> the Opera newsgroups. :-(
>
> We do. At least I do :) I only answer when I think I know something,
> though :)
That has *always* been been my experience hitherto :).
>
> There are really three possibilities a web browser has when loading a
> document that is available in its cache:
>
> 1. Load from cache.
>
> 2. Ask the server if it can load from cache.
>
> 3. Load from server.
And there is the problem - which I did not spell out in my initial
posting :(.
I "dialup" to the Internet via "wwwwoffle" and use the "wwwoffle cache"
for "download looking" at my at the URLs that opera fetched (while I
was online).
And WWWOFFLE is obsolete (I note the the package was deleted by Debian
when they released the official version of Etch - in 2006?). It is
probably also irrelevant when I will be online 24h/day.
Which means that I might have needed to learn how to use the "Opera Cache"
intelligently, if I do not want to pay my ISP for repeatedly
downloading the same URL.
I believe that all the previous replies in this thread fully addressed
my concerns. But some details need filling; e.g. a suitable size for
the Opera cache and how ofter to clean it out.
Felix Karpfen
the same URL
>
> I believe the setting for "checking" is how often opera should choose 2
> over 1. Unless you do an explicit reload, I doubt opera will choose 3
> over 2 in any case. (Except for cases where we don't trust the server
> to give us correct data otherwise.)
>
> But I don't really know. The above makes a lot of sense assuming that
> servers behave correctly. I'm sure our behaviour is to some degree
> based on our experiences with what servers actually do.
>
> Again, I doubt you'll notice much difference in this respect when
> switching from dial-up to "always on".
>
> eirik
--
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)
|
|