- From: Mark Nottingham <mnot@mnot.net>
- Date: Sun, 14 Oct 2012 06:05:43 +1100
- To: James M Snell <jasnell@gmail.com>
- Cc: Barry Leiba <barryleiba@computer.org>, HTTP Working Group <ietf-http-wg@w3.org>, Apps Discuss <apps-discuss@ietf.org>
On 14/10/2012, at 6:00 AM, James M Snell <jasnell@gmail.com> wrote: > -1 ... in my use of this I have used return-asynch and wait together (e.g. Prefer: return-asynch; wait=10)... if the server is able to process the request in less than 10 seconds, it does so and responds synchronously. If it cannot, it responds asynchronously. The mechanism works rather effectively when dealing with long running processes. I respect that you might not consider such use to be "sane" but it has proved useful nevertheless. Right, but what's the difference between: Prefer: wait=10 and Prefer: return-asynch, wait=10 ? "return asynch" really says "give me a 202" which is nonsense; the client doesn't control the status code, the server does. Cheers, P.S. I hate that "h" on "return-asynch"... :) -- Mark Nottingham http://www.mnot.net/
Received on Saturday, 13 October 2012 19:06:18 UTC