[drupal-devel] [feature] XML-RPC Engine setting in blogapi module
is superfluous and anti-usability
Bèr Kessels
drupal-devel at drupal.org
Mon Sep 19 17:44:42 UTC 2005
Issue status update for
http://drupal.org/node/31650
Post a follow up:
http://drupal.org/project/comments/add/31650
Project: Drupal
Version: cvs
Component: blogapi.module
Category: feature requests
Priority: normal
Assigned to: Anonymous
Reported by: robertDouglass
Updated by: Bèr Kessels
Status: patch (code needs review)
Makes a lot of sense. Offering options for the sake of options is plain
silly :) This sounds like such a case.
Bèr Kessels
Previous comments:
------------------------------------------------------------------------
Mon, 19 Sep 2005 17:00:28 +0000 : robertDouglass
Attachment: http://drupal.org/files/issues/blogapi.patch.txt (2.51 KB)
Here is something I wrote recently:
"The other field on the blogAPI settings page, XML-RPC Engine,
determines which is the preferred set of functions that should be used
if the publishing client supports more than one API. The options
include Blogger, MetaWeblog and Moveabletype and the recommended
default is Blogger, simply due to the larger number of functions it
supports. *There is no reason to change this setting, even if you wish
to use the MetaWeblog or Moveabletype APIs, as the setting is only
responsible for publishing the preferred API, and doesn't turn anything
on or off*.
"
(emphasis added)
Upon reviewing this, Morbus correctly asks
"If there is no reason to change the setting, because it seemingly
doesn't do anything important, why is it there?
"
Therefore this patch takes away the configurability and just defaults
to Blogger. Since it is, after all, only a preference for some form of
mostly non-existent auto-discovery, and even in the worst case doesn't
restrict the functionality, why should we bother people with it?
------------------------------------------------------------------------
Mon, 19 Sep 2005 17:32:32 +0000 : chx
Makes sense to me as the new XML-RPC library supports introspection
anyways.
More information about the drupal-devel
mailing list