Loading ...
Sorry, an error occurred while loading the content.

7Re: [rest-discuss] RESTifying

Expand Messages
  • Mark Nottingham
    Jan 7, 2002
    • 0 Attachment
      On Mon, Jan 07, 2002 at 08:42:42PM -0500, Mark Baker wrote:
      > > http://www.example.org/addresses
      > > Exposes the DB as a whole
      > > GET: representation is the main interface (queries, etc.)
      > > POST: add a new entry, returns a 303 to the created resource
      > Hmm, if you're creating a new resource it should be returned with a
      > 201. You won't get an auto redirect, but the client will know the
      > URI of the new resource. The body can also include a link if a
      > browser is your client.

      Hmm. Seems good; will have to play.

      > > http://www.example.org/addresses?repr=add
      > > GET: representation is an add form
      > /addresses could serve that purposes, no need for the new URI.
      > Content negotiation could be used to negotiate a representation
      > capable of expressing a form.
      > > http://www.example.org/addresses/thePerson?repr=edit
      > > GET: representation is an edit form
      > Again, could content negotiation not be used to retrieve an editable
      > format?

      What's the media type for an HTML form which is the editable
      representation of a resource again? ;)

      Also, how would I tell a browser to request it?

      > BTW, my other message I promised is turning into something that should
      > probably be sent to uri@..., so stay tuned.


      Mark Nottingham
    • Show all 14 messages in this topic