On Wed, Oct 13, 2004 at 08:19:47PM -0400, Robert Sayre wrote:
Well, I'd say that SEARCH has more background for querying (Microsoft implemented it long ago for Exchange, and catacomb implements it for Apache/mod_dav). Custom expect tokens, new range specifiers, etc have almost zero precedent, as far as I know.
I still find this a bit strange. An application has to insert a custom header, yet it can't alter the HTTP method? Either way, app changes are required.
That the examples that I've provided *are* defined by RFC 2616. That spec Additional HTTP methods are simply one extension mechanism; you're talking about using other extension mechanisms. Both are compliant with RFC 2616.
Looks like some wiki writing is needed :-)
I think it is also valid to ask Atom client authors whether they need all of those inputs. Does sort order matter? Are date ranges important? Or is fetching of N posts at a time sufficient?