[tahoe-dev] [tahoe-lafs] #316: add caching to tahoe proper?

[tahoe-lafs]

#316: add caching to tahoe proper?
--------------------------+-------------------------------------------------
 Reporter:  warner        |           Owner:  somebody 
     Type:  task          |          Status:  new      
 Priority:  major         |       Milestone:  undecided
Component:  code          |         Version:  0.7.0    
 Keywords:  vdrive cache  |   Launchpad_bug:           
--------------------------+-------------------------------------------------

Comment(by warner):

 I had an idea that I wanted to get down before forgetting it: we could add
 a pubsub mechanism to the storage servers (at least the current generation
 which is reached via foolscap connections), to let clients be quickly
 notified about changes to mutable shares for which they're holding a
 cached copy. They would then be allowed to hold on to their cached value
 until the pubsub channel send an "invalidated" message. We'd need to limit
 the number of subscriptions, to bound memory usage on the servers. And it
 wouldn't get us closer to our goal of fewer active TCP connections. And it
 wouldn't work with the proposed HTTP-based storage servers.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/316#comment:4>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid