From what I recall, the server was not supposed to stall the login sequence. This and the fact that you may break third-party plugins by force-closing sockets on running sessions is why I suggested using Lamport Timestamps in the first place, even though it's a disruptive change to the protocol.
These are just my random thoughts on a problem that I find interesting. Last time I looked at this code was three years ago, so you should definitely double-check on everything I say.
—
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: From what I recall, the server was not supposed to stall the login sequence. This and the fact that you may break third-party plugins by force-closing sockets on running sessions is why I suggested using Lamport Timestamps in the first place, even though it's a disruptive change to the protocol. \r\n\r\nThese are just my random thoughts on a problem that I find interesting. Last time I looked at this code was three years ago, so you should definitely double-check on everything I say."}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/673#issuecomment-375301458"}}}
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