[tahoe-dev] [tahoe-lafs] #947: Add file-with-metadata caps

tahoe-lafs trac at allmydata.org
Mon Feb 15 05:54:25 UTC 2010

#947: Add file-with-metadata caps
 Reporter:  kpreid            |           Owner:  nobody   
     Type:  enhancement       |          Status:  new      
 Priority:  major             |       Milestone:  undecided
Component:  unknown           |         Version:  unknown  
 Keywords:  inodes, metadata  |   Launchpad_bug:           

Comment(by zooko):

 Hm, the way I imagined implementing this at first was to have the client
 first fetch the associated metadata and then fetch the file. One way to
 envision the implementation would simply be to define a kind of directory
 which can only have one child link in it. Then take the cap to that
 directory and wrap it in a different cap type which means "fetch this
 directory then fetch the file it points to, applying all of the metadata
 that it contains".

 But, we could also consider bundling some metadata along with the cap
 itself. For example, if the cap is being embedded into a URL, then include
 the metadata in the URL, along with the cap. Spelling out the content type
 in standard text format e.g. {{{image/svg+xml}}} would add significantly
 to the length of the URL, but perhaps we could define a custom compression
 scheme which could represent the most common types in only a character or
 two while falling back to uncompressed form for types that we haven't
 included in our compression definition.

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

More information about the tahoe-dev mailing list