search

SDShare / Specification

SDShare - Protocol for the syndication and synchronisation of RDF
Other
10 stars 1 forks source link

202 response should not be cached #43

Closed gra-moore closed 12 years ago

gra-moore commented 12 years ago

Do we need to say that the response header when providing a 202 response should include a time to live of 0, or however you indicate that something should not be cached.

larsga commented 12 years ago

I think this is HTTP-level stuff that we should stay out of. We're saying you need to poll until you get 200. That should be enough, I think.

OK?

gra-moore commented 12 years ago

But if the server doesnt specify no cache then some intermediary could cache a not ready and keep serving it long after the data is ready. Given we are explicit and the 204 why not require a header that avoids this?

On 23 Jul 2012, at 10:56, larsgareply@reply.github.com wrote:

I think this is HTTP-level stuff that we should stay out of. We're saying you need to poll until you get 200. That should be enough, I think.

OK?

Reply to this email directly or view it on GitHub: https://github.com/SDShare/Specification/issues/43#issuecomment-7173322

larsga commented 12 years ago

What if there is no intermediary?

I think that anyone finding themselves in this situation will either realize this and avoid the problem, or find that stuff doesn't work, and then debug their environment to find out what causes it. It seems unnecessary to me to say anything, but if you really want to put it in it's OK by me.

gra-moore commented 12 years ago

Lets close this. we can always add it later if its a real world issue.