Hi Brian,

The only other place is cmsd where it wouldn't make sense to load the HTTP
protocol. Yes, the cmsd can also run multiple protocols but there is no
bridge there. Currently, xrootd and http are the only protocols but I
could imagine http2 on the horizon as well. Who knows, maybe someone brave
enough will want to add NFS4 :-)

Oddly, I see you accept http at he xrootd port. I thought hat most http
people dislike that and use he standard http port, 80. But that's a side
issue.

Andy

On Thu, 2 Aug 2018, Brian Bockelman wrote:

> Is it possible to only parse `xrd.protocol` in `xrootd` itself?
>
> We have this annoying configuration line:
> ```
> if exec xrootd
> xrd.protocol http:1094 libXrdHttp.so
> fi
> ```
>
> It's the only place where we have to use the `if exec xrootd` syntax
and I would rather not expose it to the sysadmins if we don't have to.
>
> Are there any cases where other daemons can use the protocol bridge?
If not, seems like we could keep it `xrootd`-specific until someone wants
to write a new plugin.
>
> --
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/793


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://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@abh3 in #793: Hi Brian,\n\nThe only other place is cmsd where it wouldn't make sense to load the HTTP \nprotocol. Yes, the cmsd can also run multiple protocols but there is no \nbridge there. Currently, xrootd and http are the only protocols but I \ncould imagine http2 on the horizon as well. Who knows, maybe someone brave \nenough will want to add NFS4 :-)\n\nOddly, I see you accept http at he xrootd port. I thought hat most http \npeople dislike that and use he standard http port, 80. But that's a side \nissue.\n\nAndy\n\nOn Thu, 2 Aug 2018, Brian Bockelman wrote:\n\n\u003e Is it possible to only parse `xrd.protocol` in `xrootd` itself?\n\u003e\n\u003e We have this annoying configuration line:\n\u003e ```\n\u003e if exec xrootd\n\u003e xrd.protocol http:1094 libXrdHttp.so\n\u003e fi\n\u003e ```\n\u003e\n\u003e It's the only place where we have to use the `if exec xrootd` syntax \nand I would rather not expose it to the sysadmins if we don't have to.\n\u003e\n\u003e Are there any cases where other daemons can use the protocol bridge? \nIf not, seems like we could keep it `xrootd`-specific until someone wants \nto write a new plugin.\n\u003e\n\u003e -- \n\u003e You are receiving this because you are subscribed to this thread.\n\u003e Reply to this email directly or view it on GitHub:\n\u003e https://github.com/xrootd/xrootd/issues/793\n"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/793#issuecomment-410143965"}}} [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/793#issuecomment-410143965", "url": "https://github.com/xrootd/xrootd/issues/793#issuecomment-410143965", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } }, { "@type": "MessageCard", "@context": "http://schema.org/extensions", "hideOriginalBody": "false", "originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB", "title": "Re: [xrootd/xrootd] Ignore `xrd.protocol` in non-xrootd daemons? (#793)", "sections": [ { "text": "", "activityTitle": "**Andrew Hanushevsky**", "activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png", "activitySubtitle": "@abh3", "facts": [ ] } ], "potentialAction": [ { "name": "Add a comment", "@type": "ActionCard", "inputs": [ { "isMultiLine": true, "@type": "TextInput", "id": "IssueComment", "isRequired": false } ], "actions": [ { "name": "Comment", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"xrootd/xrootd\",\n\"issueId\": 793,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}" } ] }, { "name": "Close issue", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"xrootd/xrootd\",\n\"issueId\": 793\n}" }, { "targets": [ { "os": "default", "uri": "https://github.com/xrootd/xrootd/issues/793#issuecomment-410143965" } ], "@type": "OpenUri", "name": "View on GitHub" }, { "name": "Unsubscribe", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 364196929\n}" } ], "themeColor": "26292E" } ]

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