Are you caught up in World Cup fever? |
to stop further auto updates -write Member Update Systems at 9167 ROAD 177 Oakwood, OH 45873
or visit here
| Great, according to your answer, both PUT and POST can be used to create and modify resources. So which one should be used or both must be supported for both create and update? I updated my answer to give more detail in the section "Great both can be used, so which one should I use in my RESTful I also added more tips in that same section about the tradeoffs. Brian R. Bondy Mar 10 '09 at 15:12 one cannot stress enough the fact that PUT is idempotent: if the network is botched and the client is not sure whether his request made it through, it can just send it a second (or 100th) time, and it is guaranteed by the HTTP spec that this has exactly the same effect as sending once. Jrg W Mittag M Not necessary. The second time could return 409 Conflict or something if the request has been modified in meantime (by some other user or the first request itself, which got through). Mitar Nov 27 '11 at 23:28 Yes, you are right. What would a good "catch phrase" be for idempotency in HTTP? Perhaps: "The client is not responsible for anything bad that happens if it sends the request multiple times." Jrg W Mittag Nov 28 '11 at 2:04 I think there is no difference in definition. 409 Conflict could be a result even for the first request the client made. In any case it should investigate the problem. not mistaken, what we should be stressing is that PUT is defined to be idempotent. You still have to write your server in such a way that PUT behaves correctly, yes? Perhaps it's better to say "PUT causes the transport to assume idempotence, which may affect behavior of the transport, e.g. caching." Ian Ni-Lewis Dec 28 '11 at 2:05 There are some ideas about how to make POST more reliable on Paul Prescod's website, though the site overall doesn't seem to hteverblahblah.com ... your point is quite illuminating for me, actually. The answer as it stands is already fantastic, though, don't get me wronIdempotence catchphrase? How about "Send and send and send my friend, it makes no difference in the end." should only be used to create a resource if the client cares about the resource's name. A client caring about a resource's name indicates coupling. Coupling is the result of poor practices. Therefore, use POST. If there is concern about a resource being created twice with POST (since it's not idempotent) read this answer. Joshcodes Mar 17 at 19:00 |
No comments:
Post a Comment