The client needs to reissue a request that got a kXR_wait response. As far as I recall, the idea here is not to wait for the TCP connection to die off on its own, but to wait for the plug-in code to stop acting on the requests that came through that channel. Perhaps kXR_waitresp would be a better option here since it would eliminate the wait time estimation guesswork and just notify the client asynchronously that it can proceed. Certainly it would be easier to implement in the client.
—
You are receiving this because you commented.
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 #673: The client needs to reissue a request that got a `kXR_wait` response. As far as I recall, the idea here is not to wait for the TCP connection to die off on its own, but to wait for the plug-in code to stop acting on the requests that came through that channel. Perhaps `kXR_waitresp` would be a better option here since it would eliminate the wait time estimation guesswork and just notify the client asynchronously that it can proceed. Certainly it would be easier to implement in the client."}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/673#issuecomment-375632537"}}}
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