Yep, it is not straight forward. Though for gsi and the plugins it uses it
all seems to not be additive as you have to concatenate all the key values
in one go in the parameter blob. It would seem the best idea is to look
over and enable blobbing on a case by case basis.
As for access to the config system... that was made public years ago.
Notice that XrdOucStream.hh is available in the public headers. That's
the only thing you need to get the config file directives specific to your
machine (ok, it likely needs somewhat better documentation). As far as I
can tell people just don't want to use it for what they think are simple
parameters. I mean I can simplify it even more (e.g. you give me the tags
you want in the config file and I will give you an std::vector of
key-value pairs to do whatever you want with).
Anyway, doing all of the conversion will take time as there are a lot of
other tasks that have higher priority when it comes to similar time
allocation (e.g. CRL refresh, HTTPS-xroots openSSL merging, etc). If it's
easy we can usually fit it in the cracks but for longer tasks, it will
have to wait.
On Mon, 20 Apr 2020, Brian P Bockelman wrote:
> Hi @abh3 -
>
> I'm sure that all plugins use a different syntax - as you suggest, it's likely from plugin writers working independently (and, I'd add, not having access to the configuration subsystem).
>
> However, setting up a class that generates the input string seems to be quite complicated (example question: if I specify a configuration variable multiple times, is it additive or does it replace earlier invocations) compared to simply providing access to the config system like other plugins do.
>
> No?
>
> Brian
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1016#issuecomment-616829440
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1016#issuecomment-616839926",
"url": "https://github.com/xrootd/xrootd/issues/1016#issuecomment-616839926",
"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
