I did not read the code carefully, so bear with me, but the point of moving the error callbacks to the thread pool was to make sure client holds no locks during these callbacks. I am not sure the patch you pushed helps in that regard.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@ljanyst in #257: I did not read the code carefully, so bear with me, but the point of moving the error callbacks to the thread pool was to make sure client holds no locks during these callbacks. I am not sure the patch you pushed helps in that regard."}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/257#issuecomment-315523904"}}}
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
