Well, actually we would be adding a new record type as original noted (i.e. isclose2). We don't need to add a new isXFR as that record type is easily expandable because the header already has the length of the packet and there is only one struct in that packet. The issue comes about because the isClose record can have up to three structures in it and none of those are self-describing. So, the length of the packet in the header doesn't tell you what the actual size is of any struct in it making them fixed size. What I want to do is add individual lengths to these structs.

Of course, we are ignoring the issue that once we switch to using isClose2 then for collectors that haven't been upgraded it will appear that there are no close records at all.

—
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/issues/1432#issuecomment-804512120", "url": "https://github.com/xrootd/xrootd/issues/1432#issuecomment-804512120", "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