That would be a fairly big change in the server. From the servers
perspective, a kXR_wait is fair simpler to handle because it'stateless. A
kXR_waitresp if more complicated because it has to keep state. The current
endsess path has no provision to keep state so that would have to be
added. I think Michal found it rather easy to fix the client to properly
handle the various return cases for endsess.
Andy
On Tue, 27 Mar 2018, Lukasz Janyst wrote:
> @abh3 Out of curiosity, would it be possible for the server to send `kXR_waitresp` instead `kXR_wait`? It would alleviate Eric's concerns about retry latency due to the wait time overestimation and the client-side implementation would be simpler.
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/673#issuecomment-376564635
—
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":"@abh3 in #673: That would be a fairly big change in the server. From the servers \nperspective, a kXR_wait is fair simpler to handle because it'stateless. A \nkXR_waitresp if more complicated because it has to keep state. The current \nendsess path has no provision to keep state so that would have to be \nadded. I think Michal found it rather easy to fix the client to properly \nhandle the various return cases for endsess.\n\nAndy\n\nOn Tue, 27 Mar 2018, Lukasz Janyst wrote:\n\n\u003e @abh3 Out of curiosity, would it be possible for the server to send `kXR_waitresp` instead `kXR_wait`? It would alleviate Eric's concerns about retry latency due to the wait time overestimation and the client-side implementation would be simpler.\n\u003e\n\u003e -- \n\u003e You are receiving this because you were mentioned.\n\u003e Reply to this email directly or view it on GitHub:\n\u003e https://github.com/xrootd/xrootd/issues/673#issuecomment-376564635\n"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/673#issuecomment-376566732"}}}
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
