I have not examined the xrdcp code, but I have to agree with Andy that what was going wrong with the original implementation is mysterious. The info returned to the client on redirect should include the dCache UUID. If the TPC connections 1 & 2 are opened against the redirected endpoint after that, why don't they both make use of the same opaque data? If they did, then it wouldn't matter much which one did the checksum request.

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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1359#issuecomment-743781267", "url": "https://github.com/xrootd/xrootd/issues/1359#issuecomment-743781267", "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