Can you give me an example of an order processing system which is completely 100% RESTful (i.e. retains no state whatsoever) I'm finding it difficult to envisage an order processing system that doesn't remember the orders submitted.
Steve On 06/06/07, Mark Baker <[EMAIL PROTECTED]> wrote:
On 6/6/07, Steve Jones <[EMAIL PROTECTED]<jones.steveg%40gmail.com>> wrote: > > Nothing is magic. Anything can be done poorly. So, yes, it's > > ultimately up to the developer--as everything is. But if your > > application _does_ obey REST principles (which is what is implied by > > "doing REST"), then, yes, it surely does exhibit the properties stated > > earlier. > > No... it MIGHT exhibit them. You can obey the principles of REST and > still create a pig. No Steve, you cannot (at least not a "reliability pig") because ****ALL**** RESTful systems are stateless, and all stateless systems have superior reliability to an otherwise equivalent stateful one (for the reasons Pete previously gave). Mark.
