On Jul 4, 2006, at 6:00 AM, Gregg Wonderly wrote: > UT, GET, DELETE are specified to be idempontent operations. It is the > implementation of the actions on the specified resources which make > that the > case, or not.
The contract is important here and the conract enables a client to assume that it can call DELETE as often as it likes. E.g. it can keep calling DELETE until it actually does receive a response over a bad network connection. > This is no different than any other platform for programming > remote operations todate. For some types of computing, if > idempotency is not an > issue does that mean I can't use DELETE if I can't make that an > idempotent > operation of my service implementation? Right. Because clients may be calling your DELETE more than once. That is the contract of DELETE. Jan ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
