Hi all, I'm wrestling with a protocol error condition where an action has been done already, the requester innocently asks for it to be done, and is told that it is already done. Idempotency, in a nutshell.
The problem with "already done" in an idempotent sense is that it is both an error and a success. Code-wise, it is hard to deal with quite so philosophically, it has to fall as either an error or a success not both. Does anyone feel they've got a lock on which it should be? Or should I implement a tri-state :( ? I'm currently tracing an instance of "create account" that is wending its way up through layers of results, and it's getting a bit confused. iang _______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
