> * "The resource MAY be temporary and the consumer SHOULD get it within a limited time and SHOULD NOT assume that it is available after the first time it has been requested." I think you want "successfully retrieved", not "requested". Requests can fail/be lost, connections can drop before the request hits the server. The server will no doubt define success as "I sent the 200 response", and clients as "I *received* the 200 response and parsed it successfully", but (a) nothing we can do about that (b) that's life in a distributed system. Robust server implementations might choose to add in a time delay to allow for somewhat friendlier behavior, and treat this like an asynch garbage collection problem.
Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario
