[oslc-core] Issue with Compact Rendering of a deleted (410) resource

[John Arwe]

+1 to Ian and James's replies
You should also look at how 404 is handled in this implementation.  Any 
time you code for a 410, you have to think about 404.  Seeing a 410 
instead of a 404 depends on the server keeping some record of deleted 
resources (that's the only way to tell the difference reliably between 
"gone" and "never existed").  It is unrealistic to think that all servers 
keep such historical data at all, and even those that do keep it will 
likely garbage collect it after some period of time (at which point its 
response to the same request would change from 410 to 404).

Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20110927/3ca0724c/attachment-0003.html>