Print

Print

@abh3 :

—
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://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@simonmichal in #950: @abh3 : \r\n\r\n- regarding `kXR_refresh`, just from curiosity, why shouldn't it be set for metamanagers?\r\n\r\n- regarding `kXR_NotAuthorized`, limiting the retries to 3 seems to me a very arbitrary choice ;-), I would rather make it configurable\r\n\r\n- regarding `kXR_NoSpace` and `kXR_overQuota`, I thought those are returned in case of open request with `oss.asize` cgi info, if they are meant only for writes I agree they shouldn't be retried\r\n\r\n- regarding `kXR_NoMemory` it's unclear to me what the client should do in case of a data server according to the spec (http://xrootd.org/doc/dev49/XRdv400.htm#_Toc532936559) - option B"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/950#issuecomment-485792848"}}} [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/950#issuecomment-485792848", "url": "https://github.com/xrootd/xrootd/issues/950#issuecomment-485792848", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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