1

I am trying to code an API which has a long running process to which an end user may make a POST request:

POST /things { "some":"json" }

The actual creation process can take some time, will often be queued. It might take many minutes. As a result I am not sure what I should be returning or when. Is it the usual 201 plus object, returned after whatever time it takes my API to create the object? Isn't this going to cause problems at the client end? Is there some other standard way to do this - such as an intermediate step?

I'm using Rails & Grape for my API if that helps.

dB.
  • 4,700
  • 2
  • 46
  • 51
Richard Jordan
  • 8,066
  • 3
  • 39
  • 45

1 Answers1

1

Consider whether the Post-Redirect-Get pattern suits your needs. For example, you can return a 303 redirect to some sort of status page where the client can check the progress of the request. In general, 201+object is a poor choice if the client has to wait for any appreciable period, because too many things can go wrong (what if out of annoyance or impatience he kills the browser window, or refreshes, or resubmits?)

arayq2
  • 2,502
  • 17
  • 21
  • Actually I should have come back to this q. That's exactly what I have settled on for doing, for now, though it still leaves me unsatisfied. I'll check mark you correct :-) – Richard Jordan Jan 06 '13 at 22:30