Comments on: REST: How to respond to an HTTP POST http://underground.infovark.com/2009/03/24/rest-how-to-respond-to-an-http-post/ The Infovark technology blog Thu, 17 Nov 2011 16:06:58 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Peter Obiefuna http://underground.infovark.com/2009/03/24/rest-how-to-respond-to-an-http-post/comment-page-1/#comment-539 Peter Obiefuna Mon, 12 Apr 2010 16:49:16 +0000 http://underground.infovark.com/?p=376#comment-539 Forcing all create/update events to return a redirect is a bad idea. It should still return a 201 IMO. Let the consuming client decide what to do with the returned resource uri. In most cases, it's a wasted round trip. In some cases, for instance most persons just simply return "Record created successfully" and provide a link to view/update/delete the record based on user privileges. In others, user may not even be aware that the record was created. Moreover, the create event may be a part of a composited whole. So, let the create process be concerned with what it does. Create, and return a 201 and end it's concern. Forcing all create/update events to return a redirect is a bad idea. It should still return a 201 IMO. Let the consuming client decide what to do with the returned resource uri.

In most cases, it’s a wasted round trip. In some cases, for instance most persons just simply return “Record created successfully” and provide a link to view/update/delete the record based on user privileges. In others, user may not even be aware that the record was created. Moreover, the create event may be a part of a composited whole.

So, let the create process be concerned with what it does. Create, and return a 201 and end it’s concern.

]]>