[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Implementing Atompub

To: <atom-protocol@xxxxxxx>
Subject: Re: Implementing Atompub
From: "Dirk Haun" <dirk@xxxxxxxxxxxxxx>
Date: Mon, 10 Aug 2009 20:14:21 +0200
Cc: "Toby A Inkster" <mail@xxxxxxxxxxxxxxxxx>
In-reply-to: <FB9F570A-DB95-4406-926F-3F5DEA9EB147@xxxxxxxxxxxxxxxxx>
List-archive: <http://www.imc.org/atom-protocol/mail-archive/>
List-id: <atom-protocol.imc.org>
List-unsubscribe: <mailto:atom-protocol-request@imc.org?body=unsubscribe>
Organization: Terra Software Systems
References: <FB9F570A-DB95-4406-926F-3F5DEA9EB147@xxxxxxxxxxxxxxxxx>
Sender: owner-atom-protocol@xxxxxxxxxxxx

Toby A Inkster wrote:

>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.

I would actually start with GET. That way, you can see your posts in an
AtomPub client and see if you got things like XHTML vs. plain text
formatting right. It's also a lot easier to debug.

POST/PUT can cause headaches quickly, depending on how your blog handles
IDs, for example.

bye, Dirk

--
http://www.geeklog.net/
http://geeklog.info/

Follow-Ups:
- Re: Implementing Atompub
  - From: Toby A Inkster

References:
- Implementing Atompub
  - From: Toby A Inkster

Prev by Date: Implementing Atompub
Next by Date: Re: Implementing Atompub
Previous by thread: Implementing Atompub
Next by thread: Re: Implementing Atompub
Index(es):
- Date
- Thread