Talk:Post/Redirect/Get
From Wikipedia, the free encyclopedia
[edit] Notability
"redirect after post", in quotes, yields over 11,000 results in Google, among them several notable ones, such as:
- Apache Struts calls it "a common pattern in web application development" [1]
- The Portland Pattern Repository lists it and links to examples and tutorials [2]
I can probably waste a whole lot of valuable time digging up notable sites and people reinforcing this pattern, but hopefully that won't be needed. Ubernostrum 17:42, 29 January 2007 (UTC)
[edit] Merge?
I find it hard to see what this has to do with REST. PRG has been around a lot longer than SOAP, REST and AJAX and is fundamental to making many web sites function correctly, and the lack of it is also the reason many sites still don't! I agree that this article could use some expansion, however. 24.57.191.81 17:13, 21 February 2007 (UTC)
REST was designed on the argument that there should be four HTTP operations: PUT, DELETE, POST, GET. Only the latter two are actually supported by most web browsers. The PRG pattern is an architectural "hack" that provides a work-around for the fact most web browsers still don't support PUT and DELETE. PUT and DELETE are idempotent operations. PRG is based around the fact that existing, widely-available POST and GET operations are stateless and there is no locking mechanism built into these resources. DO NOT MERGE. If anything, the request to merge is a sign that both the REST and PRG articles need housekeeping.
