Well, there were technical and non-technical issues regarding TPC. One of the main reason the rendezvous approach was taken is because it is authentication agnostic. I did not want to restrict people to particular authentication algorithms (i.e. only those that support forwarding) and I did not want to special case the code for each possible authentication algorithm as this is open-ended. Furthermore, there was no guarantee that the source and destination would use the same authentication algorithm. So, you should start seeing the devil's nest that is quickly appearing just to support some basic level of security. All of that is avoided by using a rendezvous algorithm which, from a practical standpoint, is less complicated than the alternatives if you want to do proper authentication.

Anyway, there is no reason why TPC availability could not be checked at the destination after the file is opened R/W. If support is missing then the copy could be aborted or dropped back at that point. I think the complaint is that when TPC is supported at the source but not the destination you have to wait for a timeout. From a practical standpoint that need not happen.

—
Reply to this email directly or view it on GitHub.

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