For only-if-cached ... isn't a cache supposed to return error when some non-cached data is requested?

Possibly, but this is fairly impractical. Remember the HTTP response is sent up front. So, anything after the first byte and you lose the ability to send an error.

So, for now, calling “any cached byte means the response is cached” is good enough for me.

And, also again, for direct mode proxies we should find a way to coalesce clients with the same cache-control to the same IO.

that would require some serious surgery of the OFS layer to have multiple file handles per file and it’d break the threading contracts … I think the approximations done here are not perfect but better than the more serious surgery.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/1954#issuecomment-1467125132", "url": "https://github.com/xrootd/xrootd/pull/1954#issuecomment-1467125132", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1