Working around MetaWeblog xml-rpc vagueness

The MetaWeblog API is an xml-rpc communication mechanism which I am using to post these messages from BlogEd. It is a little like Java Remote Method invocation, except that it uses xml to serialise the object states. Xml-rpc is allready very vague and imprecise, but the MetaWeblog API does not help. There are for example no agreed upon error messages as there are in HTTP. So that it is not possible to tell with certainty if an error message to a request to update a remote blog entry is telling you that
  • the password used to log in is wrong
  • the remote entry no longer exists
  • the remote entry never existed
  • some other error in the communication occurred

There is a little bit of explanatory text that will help the end user if he speaks the preferred language of the server author. In order to help BlogEd users understand the predicament I am in as a programmer I have given them all the information they need to make up their mind. Where it makes sense to give the user a choice, I pop up a dialog where they can inspect the xml-rpc messages themselves.

This makes me feel less lonely. In any case the user will probably know that he deleted an entry using the web interface a few days before.

Comments:

Post a Comment:
Comments are closed for this entry.
About

bblfish

Search

Archives
« April 2014
MonTueWedThuFriSatSun
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
    
       
Today