in reply to Re: Re: Re: [OT] Desktop applications over HTTP
in thread [OT] Desktop applications over HTTP

The "protocol" section of the original post begins to describe how to standardize on which HTTP headers to use in which ways to do "simple http post/get" type interactions.

That has already been standardised in WebDAV.

I've thought about this a fair bit, and I'm pretty sure I prefer the idea of using existing HTTP methods to view and modify data from a webserver to the extensions provided by WebDAV. For most purposes WebDAV seems like an unnecissary layer (although I understand its usefullness for something like Subversion)

<snipped interesting architecture description that sounded cool />
We'll probably add an FTP or WebDAV api so we can access our repositories from third-party applications. Our SOAP api is fine for our application but it's next to useless if we want to access our repositories from outside our app. Still, we can reuse the code in our FTP/WebDAV api.
I guess I don't think that there should be another API for the problems we're trying to solve (although what you're doing sounds neat). I think HTTP should be enough for viewing and editing content, I just think that most methods of getting the desktop involved are hooey {grin}.
I suggest using an open protocol from the beginning.
Absolutely. Hence the resistance to many of the methods of interacting with the desktop that already exist, and the affinity to HTTP.

Thanks for your response!

-- Douglas Hunter