The main reason we chose Ecto was because it has a ???console??? which makes it very useful when debugging
our XML-RPC transactions, however most of what we discuss in this section is applicable to other similar
applications. In Figure 11.5 we can see Ecto??™s main window on the left, with a list of Places articles and its
editing window on the right.
Figure 11.5 Ecto, the desktop blogging client we will be using to make XML-RPC requests, shown editing some Places content
After setting up the connection details and selecting the API we want to connect to, Ecto runs through a series
of method calls to establish the account. In our case we have chosen to use the MovableType API, however
doing so still involves calls to methods that belong to other API??™s, such as blogger.getUsersBlogs and
blogger.getUserInfo which belong to the Blogger API or metaWeblog.editPost which belongs to the
MetaWeblog API. For this reason we??™re obligated to provide those methods for our XML-RPC server.
Licensed to Menshu You
Zend Framework in Action (Ch01) Manning Publications Co. 24
Creating the interfaces
In order to work with any of the API??™s already mentioned, our application must implement the methods
required by those API??™s. If we pick an example method like metaWeblog.
Pages:
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320