[tahoe-lafs-trac-stream] [tahoe-lafs] #992: Store Content-Type 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
   Resolution:               |   Keywords:  metadata integrity
Launchpad Bug:               |
-----------------------------+--------------------------------

Comment (by nejucomo):

 Notice that {{{GET /file/...@@named=...}}} is similar to directory-
 associated edge metadata.  A URL is an edge, even when it is not stored in
 a directory.

 So in some sense, adding more features like {{{@@named}}} is similar to
 adding edge-associated metadata in a directory.

 If we add some metadata in the {{{@@}}}-style and different conventions in
 the dirnode metadata, the interface will grow more complex and confusing
 over time.  For that reason, I'm a fan of jsgf's "anonymous singleton
 directory" idea because it could replace the ad-hoc {{{@@}}} requests with
 a single standard for directory metadata.  (Maybe there are still webapi /
 ui headaches around this approach, though.)

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/992#comment:8>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage