The motivation is to measure the network behavior during a transfer.

I agree that this should go into the monitoring stream. I will close this pull request and start another when I have a draft in the monitoring stream.

This type of information makes sense to be in the "disconnect" event in the monitor, but I'm worried about backward compatibility with the monitoring stream being a binary format. Should I create a new type of monitoring event. For example, a tcp event, on the same level as an disc or open event.

I can make the other changes easily enough.

—
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/1142?email_source=notifications\u0026email_token=AA7NRDWMAXDOFKP57Z37AMLRFPED7A5CNFSM4K4LQRL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENPVMTQ#issuecomment-593450574", "url": "https://github.com/xrootd/xrootd/pull/1142?email_source=notifications\u0026email_token=AA7NRDWMAXDOFKP57Z37AMLRFPED7A5CNFSM4K4LQRL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENPVMTQ#issuecomment-593450574", "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