On Fri, 13 Nov 2009, Roy T. Fielding wrote:
Yes, and that is exactly what would happen even if HTTP supported full two-phase commit, with all of its painful consequences, if the response to commit was lost. This is an application problem, not a protocol requirement. It can be "fixed" (to the degree that any fix is possible in a distributed system) by providing the client with a status resource within the same page as the SUBMIT, such that the client can see the change in server state when it takes place even if the specific 200 response is lost. In other words, provide the client with the information necessary to check the bill before the final transaction is submitted.
It can also be checked on the server is a serial number is included in the POSTed data which can be used to determine if the original post was already processed. Dave Morris _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf