[Bugs] #613 Browse UNSP: check that browse flushes caches when memory gets tight

[Sugar Labs Bugs]

#613: check that browse flushes caches when memory gets tight
------------------------------------------+---------------------------------
    Reporter:  tomeu                      |          Owner:  erikos     
        Type:  enhancement                |         Status:  new        
    Priority:  Unspecified by Maintainer  |      Milestone:  0.94       
   Component:  Browse                     |        Version:  Unspecified
    Severity:  Unspecified                |       Keywords:             
Distribution:  Unspecified                |   Status_field:  New        
------------------------------------------+---------------------------------

Comment(by humitos):

 Well, there are two (at least) different caches on WebKit.

  1. Page Cache: this one is to keep in memory the back and forward page.
 We are not using this one at the moment.
    * http://www.webkit.org/blog/427/webkit-page-cache-i-the-basics/
    * http://www.webkit.org/blog/516/webkit-page-cache-ii-the-unload-event/
    *
 http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebSettings.html#WebKitWebSettings
 --enable-page-cache
  1. On Disk Cache: this cache keeps file on the hard disk to load web
 pages faster. This is implemented using libsoup (SoupCache), but it seems
 that we are not using this. I didn't find any related to this:
    * http://developer.gnome.org/libsoup/stable/SoupCache.html
    *
 http://webkitgtk.org/reference/webkitgtk/stable/WebKitNetworkRequest.html
    * http://developer.gnome.org/libsoup/stable/SoupMessage.html
    * How Google Chrome handles it:
      * https://sites.google.com/a/chromium.org/dev/developers/design-
 documents/network-stack/disk-cache

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/613#comment:10>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system