Currently, many plugin are configured by adding additional parameters after the plugin specification (e.g. xrootd.fslib []). This leads, many times, to inconsistent syntax and tortuously long lines (e.g. gsi) that are pretty opaque. There should be a standard way that plug-in writers can hook into the standard xrootd configuration file syntax mechanism.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1016?email_source=notifications\u0026email_token=AA7NRDV3R4J2JQPRCHDN5X3P5P7B3A5CNFSM4H5BCY3KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G5AP4KA", "url": "https://github.com/xrootd/xrootd/issues/1016?email_source=notifications\u0026email_token=AA7NRDV3R4J2JQPRCHDN5X3P5P7B3A5CNFSM4H5BCY3KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G5AP4KA", "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