Re: Hello, and some API concerns about browsing/searching

[Ken MacLeod <ken@xxxxxxxxxxxxxxxx>]

Joe Gregorio <joe@xxxxxxxxxxxxxx> writes:

> If you can handle WebDAV why bother working with the AtomAPI at all?
> 
> No really, I'm serious, if you can handle the complexity and server
> requirements of WebDAV, then why do you need that AtomAPI?

Choice of editing clients.

Also, WebDAV is an extension to HTTP, one that is not necessary for a
large proportion of Atom users.  I bring this up because sometimes
"use WebDAV" is used as the response for being able to PUT directly to
a URI ("client controlled" as Joe referred to it earlier) rather than
POST-only ("server controlled").

I'd like to point out that Atom-enabled servers are *always* in
control.  There's *nothing* a client can do that a server doesn't
allow for.

To me, the Atom API is less about "architecting" how servers and
clients should be implemented than it is about a guide to using the
web within a certain context to implement context-tailored servers and
clients.

I have a very strong concern about the Atom API not supporting
web-enabled browsers/editors that can already PUT to the web, but not
in the Atom XML Format.  They are being *excluded* from this context
*because* they are not tailored for this context.  Yet it's still
"just the web", or so I thought when we started down that road.

  -- Ken