Greetings, authors of blog-posting desktop clients! This post is for you!
Actually, this post is about you. I’ve spent the past four hours trying to implement Atom Publishing Protocol. Actually, it’s been days longer than that as I’ve been implementing and re-implementing accoring to the various documentation I’ve found online, but I’ve spent the past four hours just trying to get Ecto to work with my APP server code, and now I’m flat-out angry. It’s not just Ecto, and I’m not sure that I should only blame the Atom architects either, so let me explain my issues.
I’m trying to implement a lot of the Atom Publishing Protocol as a server. I want to be able to list blog entries, update them, and create new ones. I have written my Atom implementation to the most recent spec, and when I access the entrypoints using raw Telnet and HTTP headers over port 80, I get the appropriate responses back from my server according to the spec.
This seems great, but this is not the end of the battle – The so-called “Atom clients” I’ve been able to find just don’t seem to support the spec.