Opened at 2007-12-12T00:48:04Z

Closed at 2010-05-02T01:24:18Z

#228 closed task (wontfix)

more REST-ful PUT web interfaces (Content-Type: instead of t=)

Reported by: warner Owned by:
Priority: minor Milestone: undecided
Component: code-frontend-web Version: 0.7.0
Keywords: standards http webdav Cc:
Launchpad Bug:

Description

consider changing the current PUT $PARENTURL?t=uri (childuri) with something like PUT $CHILDURL (childurl; content-type=x-tahoe-uri

The idea is that PUTs and GETs should be symmetric, and we could use content-type on the HTTP request to indicate that we're providing the new resource by reference rather than by value.

I'm not really sure what counts as "RESTful", though, or whether it's actually a good goal to aspire towards.

Change History (4)

comment:1 Changed at 2008-06-01T20:57:08Z by warner

  • Milestone changed from eventually to undecided

comment:2 Changed at 2008-06-01T22:06:16Z by warner

  • Summary changed from more REST-ful PUT web interfaces to more REST-ful PUT web interfaces (Content-Type: instead of t=)

comment:3 Changed at 2010-04-04T22:32:35Z by davidsarah

  • Keywords standards http webdav added

The PUT ...?t=uri operation doesn't really match the intended semantics of PUT at all. It does match the intended semantics of BIND from ​draft-ietf-webdav-bind section 4, but that would require WebDAV support (#451). In the meantime it is better to use POST, since that can mean anything ;-)

I think that the idea of using a new content-type with PUT does not really help and should be rejected.

comment:4 Changed at 2010-05-02T01:24:18Z by davidsarah

  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.