Actually, the original design would handle this. It's a matter of getting
the headers promoted the right way. There is some disagreement in the
working group about what the headers should be. We are in discussion now.
Once we get that settled we will know what direction we need to take.
On Mon, 5 Jun 2023, Brian P Bockelman wrote:
> @ccaffy - setting aside the question headers, I don't think the implementation is that simple once fireflies are requested.
>
> For XrdHttp: the xrootd protocol handler only sees the requests to/from memory. I don't think it has enough information to create the fireflies -- the connection information is only known at the HTTP layer so the HTTP layer needs to be sending the fireflies.
>
> For HTTP-TPC: Similar situation. The socket is only known to libcurl. You'd need the fireflies sent at the main loop handling the transfer.
>
> So, while we're waiting on the resolution of the header values, you can probably still look at how to best construct the fireflies using the existing classes.
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/2024#issuecomment-1576836458
> You are receiving this because you commented.
>
> Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Message ID: <xrootd/xrootd/issues/2024/1576871493@github.com>
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/2024#issuecomment-1576871493",
"url": "https://github.com/xrootd/xrootd/issues/2024#issuecomment-1576871493",
"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
