Re: Implementing Atompub

[Benoît LARROQUE <benoit.larroque@xxxxxxxxxxxxx>]

From my experience with Feedbooks.com's atomPub, proceeding by 
incremental steps is really a great way to go.

We started by implanting reading (just GETing atom feeds and publishing 
a service document) with partial and full entries.
Next we added writing and deleting support (POSTing to feeds and DELETE 
on entries)
Next we added editing support (PUTing to entries)

We also added some hierarchy support based on a draft recommendation.

For now, we didn't add support for media file (images), since we lack 
support for them in our backend (maybe in the future).

Concerning tools, some kind of automated testing facilities really is a 
lifesaver, at feedbooks we use cucumber+rspec with feedvalidator (to 
check wellformedness). At the time, the APE (Atom Protocol Exerciser, 
http://www.tbray.org/ape/) didn't seem to work, but it may be a good way 
to start checking your implementation.

Good luck with the implementation

Benoit

Toby A Inkster wrote:
> Hello all,
>
> I'm looking for advice on how to implement Atompub in my blogging/CMS 
> tool demiblog <http://demiblog.org/>.
>
> There doesn't seem to be an awful lot of guidance for developers on 
> how to implement Atompub. There's the RFC of course, which is a 
> definitive source of information, and fairly well-written and clear 
> from what I can tell, but I'm looking for tips on "where to start?"
>
> What is a minimal useful subset of Atompub that I should implement first?
>
> POST/PUT of atom:entry elements seems to be a good start to me. If I 
> just implement this to begin with, is that enough for Atompub clients 
> to be able to add and edit blog entries? Or are things like 
> workspaces, service documents, etc vital for them to work properly?
>
> I do eventually hope to implement Atompub in its entirety, but am 
> looking for quick wins first.