I tried to do a little research on Moodle's ability to use PEAR extenions and what I find is confusing in that it seems that Moodle supports use of PEAR in some cases and not in others (e.g. XMLRPC)
Does someone have a table of what is needed, what can be used from PEAR and what can't that can be posted to the documentation.?
Additionally, is there an internal commitment to make use of PEAR in that PEAR arguably makes it so much easier to manage extensions? And if so, what is the situation on employing PEAR xmlrpc for moodle networking?
Our general policy is to make Moodle standalone and independent of PEAR. PEAR has not been as reliable as you might think (eg not included on cheap web hosts etc).
Where we've used PEAR extensions we've included copies in Moodle core, and gone through some trouble to allow them to be licensed as GPL to make this legal:
http://docs.moodle.org/en/Credits
Most of the PEAR libraries are accessed by some other API in /lib, and sometimes these will go to the trouble of checking and using a real separate PEAR version if it exists, and only falling back to the included version if necessary. This is the preferred way to handle these things.
Where we've used PEAR extensions we've included copies in Moodle core, and gone through some trouble to allow them to be licensed as GPL to make this legal:
http://docs.moodle.org/en/Credits
Most of the PEAR libraries are accessed by some other API in /lib, and sometimes these will go to the trouble of checking and using a real separate PEAR version if it exists, and only falling back to the included version if necessary. This is the preferred way to handle these things.
As asked here: http://moodle.org/mod/forum/discuss.php?d=98420 since moodle networking is the apparent direction of future development, is PEAR xmlrpc going to be addressed? Will someone identify whether there are or will be options here?