Branching off of #537434: Drop the blog API from core, we now have xmlrpc.php, includes/xmlrpc.inc and includes/xmlrpcs.inc, along with its hook, that are being used by absolutely nothing in Drupal core. The forked library is also extremely old and outdated. Since it's not being used by Drupal core, this should move to a solution like Services, which abstracts the communication layer between the client and the server.

CommentFileSizeAuthor
no_xmlrpc.patch41.76 KBrobloach

Comments

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

I'm personally not okay with dropping this without a suitable replacement. If Services module gets into core, great. If not, I see no particular reason to *remove* flexibility from our framework.

Core doesn't use our node access system either; that's no reason for a web framework not to ship with the capability to limit access to nodes. So too with shipping with protocols for external libraries to interact with Drupal.

chx’s picture

chx commented
Status: Needs review » Closed (won't fix)

This would be really foolish, are you going to drop all the alters and node access just because it's not used by core?

chx’s picture

chx commented

Also, I am going to delete the tag smallcore from this issue and from drupal.org. http://buytaert.net/8-steps-for-drupal-8 let's stop saying smallcore.

carlos8f’s picture

carlos8f commented

I agree w/ chx, XML-RPC is general enough and useful enough to have in core. It doesn't matter if the library is old, it still works :) I developed a very large site last year that used XML-RPC all over the place, and I was very glad that Drupal had all the tools I needed out-of-the-box.