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

Re: Implementing Atompub

To: <atom-protocol@xxxxxxx>
Subject: Re: Implementing Atompub
From: "James Holderness" <j4_james@xxxxxxxxxxx>
Date: Tue, 11 Aug 2009 00:24:42 +0100
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>
References: <FB9F570A-DB95-4406-926F-3F5DEA9EB147@xxxxxxxxxxxxxxxxx> <20090810181421.856120548@xxxxxxxxxxxxxxxxxxx> <2EDACFAF-E555-4512-9F8D-2BD9544ECB28@xxxxxxxxxxxxxxxxx>
Sender: owner-atom-protocol@xxxxxxxxxxxx


Toby A Inkster wrote:

That certainly makes sense. How good are Atompub clients at sendingsensible HTTP Accept headers? I'd like to avoid defining separate URLsfor the Atom and XHTML representations of a page if at all possible.

I don't know about Atompub clients, but Atom feed readers typically justsend */* as their Accept header or nothing at all. At least that was thesituation last time I checked.


Regards
James

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

References:
- Implementing Atompub
  - From: Toby A Inkster
- Re: Implementing Atompub
  - From: Dirk Haun
- Re: Implementing Atompub
  - From: Toby A Inkster

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