[tahoe-dev] [tahoe-lafs] #992: Store Content-Type as part of directory entries (was: Store content-type and encoding as part of directory entries)

[tahoe-lafs]

#992: Store Content-Type as part of directory entries
--------------------------------+-------------------------------------------
 Reporter:  jsgf                |           Owner:  somebody 
     Type:  enhancement         |          Status:  new      
 Priority:  major               |       Milestone:  undecided
Component:  code                |         Version:  1.6.0    
 Keywords:  metadata integrity  |   Launchpad_bug:           
--------------------------------+-------------------------------------------
Changes (by davidsarah):

  * keywords:  => metadata integrity
  * owner:  nobody => somebody
  * type:  defect => enhancement
  * component:  unknown => code


Comment:

 #994 discusses Content-Encoding in more detail -- it is not sufficient to
 ''just'' store the Content-Encoding as metadata; the frontends also have
 to be able to decompress a compressed file in some cases.

 Also, I don't think that storing Content-Encoding in '''edge''' metadata
 can work. The edge metadata isn't known when referring to a file directly
 by its cap, rather than via a directory, so the interpretation of the file
 as a sequence of bytes (never mind as a MIME object) would be ambiguous.

 Changing this ticket to just be about Content-Type (and perhaps other edge
 metadata that Tahoe would not need to understand).

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