Print

Print


@smithdh : thanks a lot for the PR. OK I see this is handling the case when w have Bothe read and write events, and on the read event there's an error and the socket gets disconnected, in this case we are not suppose to handle the write event, is this correct?
Is this only a problem in case the stream gets reconnected and assigned to a different event loop, or is this a problem in general because the stream got closed and the write event is invalid?


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/pull/1935/c1445999289@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/1935#issuecomment-1445999289", "url": "https://github.com/xrootd/xrootd/pull/1935#issuecomment-1445999289", "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