I'm not claiming that doing the "expected" reads is proper behaviour
either. In fact, it does limit ones ability to determine if the received
size is correct. For instance, if I pattern my reads I *might* (not with
RAL) determine if the file is shorter than I expected but I will never
know if the file is actually longer than expected. So, you see the
conundrum.
On Thu, 5 Aug 2021, Albert Rossi wrote:
> That may be true, Andy, but it seems your client is much more "defensive" than mine, since they were encountering this problem only with dCache destination endpoints ...
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1454#issuecomment-893686767
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1454#issuecomment-893715243",
"url": "https://github.com/xrootd/xrootd/issues/1454#issuecomment-893715243",
"name": "View Issue"
},
"description": "View this Issue 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
