[tahoe-dev] [tahoe-lafs] #329: dirnodes could cache encrypted/serialized entries for speed

[tahoe-lafs]

#329: dirnodes could cache encrypted/serialized entries for speed
---------------------------+------------------------------------------------
 Reporter:  warner         |           Owner:  kevan    
     Type:  enhancement    |          Status:  new      
 Priority:  minor          |       Milestone:  undecided
Component:  code-dirnodes  |         Version:  0.8.0    
 Keywords:  dirnode        |   Launchpad_bug:           
---------------------------+------------------------------------------------

Comment(by kevan):

 Okay, I've got tests in place -- I'll attach them in a bit.

 One minor nit: I was working on the assumption that {{{_pack_contents}}}
 and {{{_unpack_contents}}} were inverses -- i.e., if I do
 {{{_pack_contents(_unpack_contents(string))}}}, I should get {{{string}}}
 back. I made this a condition in my test function, but it failed --
 {{{_pack_contents}}} would return a different string, even when fed with
 the unmodified dict returned from {{{_unpack_contents}}}. But all of the
 data inside the dict seem the same -- at least the rocaps, rwcaps, and
 metadata. Is this normal?

 Also, the hardcoding of the base32-encoded representation of that
 directory tree is kind of horrific -- any ideas for a better way of doing
 that?

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