On 10/11/05 12:21 AM, "James Holderness" <[EMAIL PROTECTED]> wrote:
> Eric Scheid wrote:
>
>>> The question I have is why the need for the app:seek attribute? Would it not
>>> be simpler to just predefine the exact format of the query string?
>
>> Depends on the arguments style of the server software.
>>
> Surely the server is being written to support the Atom protocol? The argument
> style would be whatever the Atom protocol specified it should be. With
> everything that has been said about simplifying the protocol and not including
> things that aren't strictly necessary, this level of freedom really doesn't
> seem justified. Unless there's some other use that I'm missing.
What I mean is that some servers will be implemented using one code base,
and other servers different code bases. Some will expect URL arguments in
this form:
http://example.com/feed.cgi?a=1&b=2&c=3
while another looks like this
http://example.com/cgi-bin/foo?a:1;b:2;c:3
and so on. It's not really a simple matter of freedom of choice -- some
server environments just don't allow nice clean URLs.
We don't legislate that atom feeds end with .atom, allowing feed.php,
feed.xml, etc; so why should we legislate the form of app:seek?
e.
