On Wednesday, January 8, 2014 10:40:21 AM UTC-8, Bruno Jouhier wrote: > > > I find it a bit strange to have the POST use the location returned by a > GET in the second part (the answerer). I would have expected the reverse > but this is how the example was setup. > > Bruno > > Yes, it is a bit strange. Each GET request for an offer includes a "Location" header that specifies the location that a subsequent POST should use to identify a reply to that specific offer. (This way, if the offer expires, is responded to, and/or gets replaced in the intervening time, the server can correctly identify that the reply should be rejected.)
I admit that this is a considerable departure from the "Location" header's customary semantics. I'll probably change it to something like "Reply-Location" in a pending revision of the protocol. (I had forgotten about the "Link" header, and was using "Location" to mean the same thing, minus the crucial attributes of "Link"s.) -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
