7Re: [rest-discuss] RESTifying
- Jan 7, 2002On Mon, Jan 07, 2002 at 08:42:42PM -0500, Mark Baker wrote:
> > http://www.example.org/addressesHmm. Seems good; will have to play.
> > 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.
> > 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=editWhat's the media type for an HTML form which is the editable
> > GET: representation is an edit form
> Again, could content negotiation not be used to retrieve an 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 shouldCool!
> probably be sent to uri@..., so stay tuned.
- << Previous post in topic Next post in topic >>