e hënë korrik 05, 2004

Edited further in the Roller UI.

Last month my faithful Treo 180 died, from a predictible death by a hip fracture... sorry by a fracture of the flip top hinge (these models were doomed at birth). Since my wife is pregnant, due in 2 months, I want her to be able to reach me all the time, so I shopped for a new phone.

I've Read Russel's Notebook a bit, bought a few magazines and did some quick research to determine that the so called smartphones are not yet for me. Not smart enough, and for serious use I need a keyboard. It must be a generation issue: I must be part of the last generation who don't have developped the ability to type with 10 digits keyboards:-)

So I went for a Treo 600, which had the advantage of being ready to use with my accumulated agenda and contacts from the past 8 years that I've used Palm devices.

I've used the Treo 180 only as a phone/PDA, sending a few SMSes buth that's it. With the Treo 600 I decided to start playing with the online capabilities of the device. I already tried 2 mail clients but none of them handles IMAP over SSL with my self signed cert powered personal IMAP server. I need to do more search and debug on that.

Then I shopped for a blogging client: my colleague Matt Ingenthron has posted in the internal bloggers mailing list that he has tested mo:blog successfully, so I gave it a try too.

The first 2 lines of this post have been posted from my Treo 600 phone: it works really well.

However I tried the fancy feature which lets you post pictures taken with the Treo's built in camera, using the MetaWeblog API call newMediaObject I suppose... and it failed: my son Simon's picture has not been uploaded to the server.

I did not sniff the http traffic (it goes from my phone operator to blogs.sun.com, I need to test this with my own server, whenever i have time to set it up).

But a quick look at Roller source told me I don't need to go further:

In package org.roller.presentation.xmlrpc

public class MetaWeblogAPIHandler extends BloggerAPIHandler
...
    public Object newMediaObject(String blogid, String userid, String password, 
                                 Object struct) throws Exception
    {
        mLogger.info("newMediaObject() Called =[ UNSUPPORTED ]=====");
        mLogger.info("     BlogId: " + blogid);
        mLogger.info("     UserId: " + userid);
        mLogger.info("   Password: " + password);

        throw new XmlRpcException(UNSUPPORTED_EXCEPTION, 
                                  UNSUPPORTED_EXCEPTION_MSG);
    }

I hope the Atom posting API becomes more widespread, on client and servers, because the mishmash of APIs that are used right now make it too difficult for client developers to create clients which work with every servers. Even with the NetNewsWire client I use to post to this Roller powered weblog I have some trouble sometimes.

Until that happens I may give a try to completing the MetaWeblog API implementation for Roller: after all that's not very complicated, there is a directory for resources for each user already, so it's just a matter of Base64 decoding the bits and creating the file with the name specified in the struct.

In Open source Java libraries for Weblogs, Wikis, and Newsfeeds Dave Johnson (Roller creator) wonders:

One question that crossed my mind: should Rome include a blogging client library? Posting, updating, and deleting posts via the XML-RPC based Blogger API or the REST-based Atom API is not exactly easy to do. Wouldn't it be nice to have a client library with an easy-to-use set of interfaces for this.

Rome is the open source java library that Alejandro, Elaine and I have started a month ago to unify Syndication feed parsing in java. I think a posting API to abstract out the various protocols is a good idea as a Rome subproject: we're busy preparing our 0.3 release for now, with unit tests and various subprojects that got started by our new developers, but Dave, feel free to get a Rome subproject started on that.

calendar

search

navigation

links

rss feeds

referers

Today's Page Hits: 10