On 01/30/2010 12:31 AM, Vladimir Dronnikov wrote: > > When one operation (paying a bill, say, PUT <>(amount=1)) depend on > another (counting the saldo, GET <>/saldo), the whole scheme becomes > rather synchronous -- thus transactions -- and they heavily resemble > database's ones. >
Agreed, though a RESTful transaction would be something like the proposed "Reliable HTTP" where the client can be sure whether the operation was completed or not. > Right. But real applications rarely do delete something. Besides, the > real world doesn't cascade. > Content management systems should have deletion available. Though I agree, better mark it unavailable, or move to an archive table than actually remove the resource. I don't quite understand what you mean by the real world not cascading? Vlad -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
