I copied dillorc into ~/.dillo/ and set "use_dicache=YES". I then went into Dillo (0.7.1) and went to Google. (I'm on a 33.6K modem connection so I can see the time it takes to load the Google logo). Then I went out of Dillo and back in again to the Google home page. The Google logo took just as long to draw as the first time. I thought that the dicache setting would keep the images in a cache. Obviously I don't understand how this is supposed to work. Bill
On Mon, 10 Mar 2003 20:08:24 +0000 William Trenker <wdtrenker@yahoo.ca> wrote:
I copied dillorc into ~/.dillo/ and set "use_dicache=YES". I then went into Dillo (0.7.1) and went to Google. (I'm on a 33.6K modem connection so I can see the time it takes to load the Google logo). Then I went out of Dillo and back in again to the Google home page. The Google logo took just as long to draw as the first time. I thought that the dicache setting would keep the images in a cache. Obviously I don't understand how this is supposed to work.
Bill
_______________________________________________ Dillo-dev mailing list Dillo-dev@lists.auriga.wearlab.de http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev
I thought that dillo doesn't have a persistant cache - I thought that the understanding was that if you want a cache, then you can install one yourself, like squid. Squid would probably be the best way to do this, I will be installing it soon (when ever I work out how on earch the configuration works!). But, that dicache thing is interesting (I am not a Dillo developer...)
Hi guys, Let me clarify a little bit about what the dicache is. This is how Dillo works. When you ask for a URL (be it a root URL, like a HTML, or an image embedded in a page), it looks it up in a _memory_ cache. If it's already there it returns the content of the cache, and if not it makes a connection to retrieve that URL. But there is a complication with respect to images. The images which are downloaded need to be decompressed to be displayed (that is, transformed from their original format, jpeg, gif, etc, to a bitmap format). So for images, first the dicache (_d_ecompressed _i_mage cache) is checked, then the cache, then finally it is retrieved from the site. The problem with dicache is that it eats up a *LOT* of memory, and the only benefit is the processing time of transforming from the original format to the bitmap. That's why the default is NO. TheStar writes:
On Mon, 10 Mar 2003 20:08:24 +0000 William Trenker <wdtrenker@yahoo.ca> wrote:
I copied dillorc into ~/.dillo/ and set "use_dicache=YES". I then went into Dillo (0.7.1) and went to Google. (I'm on a 33.6K modem connection so I can see the time it takes to load the Google logo). Then I went out of Dillo and back in again to the Google home page. The Google logo took just as long to draw as the first time. I thought that the dicache setting would keep the images in a cache. Obviously I don't understand how this is supposed to work.
Humm... I wonder how you got to that impression. Are the docs fuzzy anywhere abou this issue? We can try to clear it up. Anyway, as I explained dicache is a _memory_ cache. It never gets persisted, so when you leave Dillo, it's all gone.
I thought that dillo doesn't have a persistant cache - I thought that the understanding was that if you want a cache, then you can install one yourself, like squid. Squid would probably be the best way to do this, I will be installing it soon (when ever I work out how on earch the configuration works!).
Exactly. Beware though that there are simpler web caches then Dillo, I forget their names right now... 'wwwoffle' is a famous one I think, but there are others. Google around. There is some nice information that comes with Dillo with respect to caches and dicaches. Read dillo/doc/Cache.txt and dillo/doc/Images.txt. regards, -- Livio <livio@ime.usp.br>
Livio Baldini Soares writes: [...]
I thought that dillo doesn't have a persistant cache - I thought that the understanding was that if you want a cache, then you can install one yourself, like squid. Squid would probably be the best way to do this, I will be installing it soon (when ever I work out how on earch the configuration works!).
Exactly. Beware though that there are simpler web caches then Dillo, ^^^^^
Squid!
I forget their names right now... 'wwwoffle' is a famous one I think, but there are others. Google around.
-- Livio <livio@ime.usp.br>
I copied dillorc into ~/.dillo/ and set "use_dicache=YES". I
William, then went into Dillo (0.7.1) and went to Google. (I'm on a 33.6K modem connection so I can see the time it takes to load the Google logo). Then I went out of Dillo and back in again to the Google home page. The Google logo took just as long to draw as the first time. I thought that the dicache setting would keep the images in a cache. Obviously I don't understand how this is supposed to work. The dicache is the decompressed image cache. It avoids decoding the image every time it is rendered as it caches the RGB. You may read doc/Cache.txt Cheers Jorge.-
participants (4)
-
Jorge Arellano Cid -
Livio Baldini Soares -
TheStar -
William Trenker