[wp-xmlrpc] Wordpress version from xmlrpc?

[Kimmo Suominen]

Shouldn't clients just use system.listMethods to discover available
methods (i.e. supported features)?  This way the client can choose
the methods it likes best, and can avoid using ones that are not
available.

Using hard-coded knowledge on the client end would prevent using new
methods added on-the-fly or e.g. by backporting features to an older
version of WordPress.

Exposing a single API revision number is practically equivalent to
exposing the WordPress version number.  I'd rather not disclose
information like that when not necessary.  Software version numbers
should not be relevant to the network protocols.

Having each method somehow support multiple versions of a protocol
(e.g. different calling conventions) seems complicated.  Clients
probably wouldn't know how to check for a WordPress-specific API
revision for each method.  It would be better to extend methods
in a backwards compatible way, e.g. using named arguments in an
array.  If backwards compatibility cannot be maintained in a method,
it probably means it should become a new method instead.

Best regards,
+ Kimmo
-- 
<A HREF="http://kimmo.suominen.com/">Kimmo Suominen</A>

On Sat, Jan 12, 2008 at 02:32:07PM -0700, Joseph Scott wrote:
> 
> On Jan 12, 2008, at 8:27 AM, Carlos Moffat wrote:
> 
> >Hi,
> >
> >At the risk of having miss something obvious (again): is the wordpress
> >version exposed through xmlrpc?
> 
> 
> As far as I've seen it isn't.  One thing I've toyed with though is  
> providing some sort of API revision number.  This could be used by  
> clients to figure out what features are supported.  At some point  
> I'll submit a ticket+patch for that to get more discussion on it  
> rolling.
> 
> --
> Joseph Scott
> http://joseph.randomnetworks.com/