 |
 |
Just an update. We are working on a simple solution but it seems simple is not in the cards. Whatever the solution, it likely requires that you use an R5 client. It cuts in two ways, either we update the client to effect a split data path or we require the client to use TLS to effect the split data path (the latter only requires server-side changes). The data path doesn't need to use TLS, we just need TLS to securely do the split from the control channel. However, TLS is only available in R5. So, either way we are stuck to requiring R5 on both ends. What I mean by R5 is that the server and client be at release 5. We don't see any way we can make this backward compatible other than the standard fallback of using the slow connection for the data (which we would do, by default, for backward compatibility). Is that going to be a problem for you? Would you like at least the option if the client is not R5 to either use the slow path or just terminate the request? -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1192#issuecomment-631302622 ######################################################################## 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