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

10168Re: Introductory REST Article

Expand Messages
  • Ebenezer Ikonne
    Jan 2, 2008
    • 0 Attachment
      This works as in your sample "submit" means "create". If submit was
      a distinct operation from create, you would have to do something
      different. Any thoughts on that?
      --- In rest-discuss@yahoogroups.com, Stefan Tilkov
      <stefan.tilkov@...> wrote:
      > I've chosen to map "submit order" to a POST to the collection
      > identified by /orders. The POST would return the URI of a new
      > (the order) in a Location header.
      > For a generic client, everything should be fine since this is just
      > standard behavior. (Another option would have been to use PUT,
      > the downside of the client having to choose the URI, and the
      > of being idempotent.)
      > For a client that's aware of the business semantics, it means
      > submitting an order. Of course this would have to be communicated
      > means of documentation, possibly via some click-through agreement.
      > Stefan
      > --
      > Stefan Tilkov, http://www.innoq.com/blog/st/
      > On Jan 2, 2008, at 6:05 PM, Ebenezer Ikonne wrote:
      > > Even in an internal system, "submit" could mean something else. It
      > > could indicate the need to process or fulfill the order. These
      are the
      > > type of operations most people that I know are interested in REST
      > > to see demonstrated.
      > >
      > >
      > >
    • Show all 25 messages in this topic