Print

Print

So, I've looked at this in several angles and he only way to do this is for plugin writers to use the standard interface to get to read the configuration file and parse out what is of interest. I suppose we could make it slightly easier but it would reduce the options available. I'll open it up to suggestions of what plugin writers would like to have and after a little while, if I don't get any feedback, close this issue as one that is not particularly interesting.

—
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-606429964", "url": "https://github.com/xrootd/xrootd/issues/1016#issuecomment-606429964", "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