[wp-xmlrpc] Decoupling xmlrpc endpoint from Wordpress installation

[Eric Mann]

I'd need to see some pseudocode describing how your XMLRPC interface is working.
 A well-decoupled interface would work whether data was missing or not ... so it
sounds like you're just not handling cases where incomplete data is passed to
the system.

On July 20, 2010 at 2:26 PM Luke Mackenzie <luke at lukem.co.uk> wrote:

> Hi,
>
> I'm working on a Wordpress MU install (2.9.2) and have developed some custom
> XMLRPC methods which are working fine. However, we're in a situation where the
> XMLRPC endpoint is serving live clients (flash kiosks) and the actual
> wordpress website is not yet live so is still being developed (theme
> development, new /updated plugins etc). Updates to the live server (templates,
> new custom fields, people adding new content) are occasionally causing
> instabilities with the flash kiosks (the flash is expecting a custom field to
> exist, for example, and someone has removed it from the authoring interface or
> someone adds content with a vital image missing).
>
> Can anyone suggest a strategy for decoupling the XMLRPC interface from the
> live site? Would this need database replication or something similar? Maybe we
> could have an additional blog which only serves the kiosks and replicate data
> to that at 24 hour intervals?
>
> Many thanks,
>
> Luke.
> _______________________________________________
> wp-xmlrpc mailing list
> wp-xmlrpc at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-xmlrpc