 |
 |
In this case - yes, there's harm. We look for the org.dcache.uuid key to identify the remote host as dCache. If it's present, we change how we re-build the tried= string if the pool host fails. I'm starting to wonder - should we have a plugin point so the client can influence redirections (i.e., affect the opaque information or decide to abort the recovery / ignore kXR_redirect)? Can you update the documentation of that line in XrdClFile.hh to denote which key affects file opens? --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/162#issuecomment-63308977 ######################################################################## 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