Comments on: Forms on the Web and the Missing Stubs http://www.lixo.org/archives/2008/07/31/forms-on-the-web-and-the-missing-stubs/ letting the problem solve itself Wed, 07 Jan 2009 11:58:45 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Websites tagged "simpledb" on Postsaver http://www.lixo.org/archives/2008/07/31/forms-on-the-web-and-the-missing-stubs/#comment-47154 Websites tagged "simpledb" on Postsaver Sat, 04 Oct 2008 10:02:31 +0000 http://www.lixo.org/archives/2008/07/31/forms-on-the-web-and-the-missing-stubs/#comment-47154 [...] - Forms on the Web and the Missing Stubs saved by JohnEmersonsFoot2008-10-04 - Thinking about Cloud Computing saved by chaoyangzhu2008-10-03 [...] [...] - Forms on the Web and the Missing Stubs saved by JohnEmersonsFoot2008-10-04 - Thinking about Cloud Computing saved by chaoyangzhu2008-10-03 [...]

]]> By: Jim Webber http://www.lixo.org/archives/2008/07/31/forms-on-the-web-and-the-missing-stubs/#comment-44178 Jim Webber Fri, 01 Aug 2008 09:32:58 +0000 http://www.lixo.org/archives/2008/07/31/forms-on-the-web-and-the-missing-stubs/#comment-44178 Hey Carlos, I actually think you'd want to PUT your fee payments to a URI generated by the server. This has two advantages over the POST scheme you suggest: 1. It's more like real-life. The attendant tells you where to go pay. 2. It's idempotent, so in a failure case you can re-try without risking the loss of more cash. Jim Hey Carlos,

I actually think you’d want to PUT your fee payments to a URI generated by the server. This has two advantages over the POST scheme you suggest:

1. It’s more like real-life. The attendant tells you where to go pay.
2. It’s idempotent, so in a failure case you can re-try without risking the loss of more cash.

Jim

]]> By: Rafael Ferreira http://www.lixo.org/archives/2008/07/31/forms-on-the-web-and-the-missing-stubs/#comment-44141 Rafael Ferreira Thu, 31 Jul 2008 21:48:40 +0000 http://www.lixo.org/archives/2008/07/31/forms-on-the-web-and-the-missing-stubs/#comment-44141 Shouldn't the STUB be embedded in URIs contained in the body of the passport representation? From your example, I got the impression that clients are generating URIs, which is a huge no-no as far as REST goes. Shouldn’t the STUB be embedded in URIs contained in the body of the passport representation? From your example, I got the impression that clients are generating URIs, which is a huge no-no as far as REST goes.

]]>