Writing a XML-RPC server for a framework such as MODx is no trivial task (as I am painfully learning). There are lots and lots and lots of potential security mistakes to make, leaving your database open to any number of attackers.
There are a couple of things I would suggest for you to get in line before you start writing you xmlrpc server for MODx Xsss4hell:
Start with an already established method for managing XML-RPC Methods. I chose to base my server on The Incutio XML-RPC Library for PHP (
http://scripts.incutio.com/xmlrpc/ ).
Second, you should get yourself intimately familiar with the MODx database structure and, as I found out into my project, you should understand how to instantiate a new documentParser by include the document parser class in the manager’s includes folder. That way, you will have access to the MODx document object and the objects that snippet developers have access to such as the DBAPI and $modx->getAllChildren(). And one of the things I found out late in the game, re-syncing the site cache map by including cache_sync.class.processor.php and instantiating a new synccache();.
When you are comfortable enough with all that, then comes the hard part of learning the Blogdesk API. I haven’t looked at their site, but if you are lucky, then they have it documented there, and maybe even have a support forum. You will have to understand how their API works to translate between Blogdesk and MODx. then, once you understand both the MODx backend AND the Blogdesk API, you should be able to write an XML-RPC server for MODx with functions to gather and set data based on hooks from the blogdesk API.
This is going to be a HUGE challenge, so I wish you much luck Xsss4hell. Be persistent, stick with it, and I am sure you can achieve your goal of writing an XML-RPC server for MODx <--> Blogdesk!
Keep us posted with your progress Xsss4hell.
-sD-
Dr. Scotty Delicious, Scientist.