 |
 |
1. The client only needs to check for fatal errors at that point. The poller is supposed to be level-triggered, so, if the connection was successful, when the socket becomes ready to write, the client should be notified about this fact. This is because the client has subscribed to the write notifications for this socket. 2. The client doesn't expect to receive read notification for this socket at this point, because it has not asked to be notified about read events for this socket at this point. The problem is a race on poller init. --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/5#issuecomment-17112122 ######################################################################## 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