On 3/13/06, Thomas Broyer <[EMAIL PROTECTED]> wrote: > I also think many people here will disagree with the docstring (see > below), saying you can POST only Atom Entries to entry collections: > > def testMissingContentType(self): > """POST an entry with no Content-Type header. > It MUST fail since entry collections > only accept Atom Entries. > """
Good catch, that was a leftover restriction from -07, which mandated that only entries could be POSTed to an entry colleciton. Now that -08 has loosened that restriction it makes it much harder to test an APP implemementation, and I strongly disagreed with changing the spec for this very reason. If you want a 'kitchen sink' collection that takes anything and turns it into an entry then create a new collection type and use that instead. The fundamental problem here may sound hauntingly familiar: ""Here is a collection, it might accept only entries, or it might accept PNGs, JPEGs and multipart-mime. It can't tell you and you can't guess."" I will update the test suite by removing the test completely since the client has no way of telling what an entry collection can accept. -joe > > Namely, James M Snell told us how he's posting images (or any other > "media") to an entry collection and have the server automatically > generate an Atom Entry. > And I also think many people agree on POSTing > multipart/related;type="application/atom+xml" to entry collections as > well. > > For the record, the -08 draft says nothing about what can be POSTed to > an entry collection. > > -- > Thomas Broyer > > -- Joe Gregorio http://bitworking.org
