 |
 |
Hi Brian, Well, logically yes. But here are some qualifications 1) If we provide a dynamic "add plugin" interface we setup a catch22 situation since there really is no way for the plugin plugin to be versioned. 2) If we provide an external mechanism (e.g. read some file somewhere) we've complicated the lives of many people. Which pill do you want? Andy -----Original Message----- From: Brian Bockelman Sent: Monday, September 17, 2012 5:21 AM To: xrootd-dev Subject: Extended version checking to third party plugins Hi, I'm developing a few plugins: - The caching proxy needs to be able to load the XrdOss plugin - I'm doing a new plugin interface which allows the admin to load a "decision plugin", a pluggable interface for whether the "caching" part of the caching proxy should be triggered. However, the version checking in XrdSysPlugin appears to be hardcoded such that it can only be used for Xrootd-internal plugins. I'd really like to avoid maintaining a complete copy/paste of all that code just to add version checking. Is it possible to extend this code so external projects can use it? Brian ######################################################################## 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 ######################################################################## 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