True. Brian has his own agenda, not that I'm quibling about this one. Good
to know. So, I will put my focus on what we can do to make this future
proof. However, I am at the end of my useful attention span (it is 3 AM)
so it will have to wait for tomorrow.
Andy
On Tue, 30 Jun 2020, Elvin Sindrilaru wrote:
> The basic tests that I've done with GSI work as before. The Crypto patches add just one new API (X509ParseStack) so in principle should not affect any of the previous behavior. Initially, I favored a more ad-hoc approach where all this would still be contained in the Http part but Brian wanted to have this functionality logically grouped in the Crypto part as conceptually that makes more sense.
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/pull/1231#issuecomment-651683929
—
You are receiving this because you are subscribed to this thread.
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/pull/1231#issuecomment-651687609",
"url": "https://github.com/xrootd/xrootd/pull/1231#issuecomment-651687609",
"name": "View Pull Request"
},
"description": "View this Pull Request 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