On Fri, Nov 5, 2010 at 4:51 PM, David Overcash <funnylookin...@gmail.com> wrote: >> >> Our current reasons to switch to HTTP is that HTTP is ubiquitous-- often >> already available at institutions, usually requires no additional >> training to make something available, and has no firewall/security >> concerns. I wonder if WebDAV still gives us those benefits. > > Sorry - coming into this a bit late... but it seems to me that HTTP would > make the most sense when bundled with some standard we created for directory > listings, modules, etc. In addition to being widely supported, it is also > easy to use HTTPS to create simple-encryption in addition to it being easily > accessed through just about any proxy service (if necessary). > I know that it would make much more sense to use HTTP when it comes to > mobile platforms (speaking from experience). > -David
a) WebDAV is a _SUPERSET_ of HTTP. So HTTP GET, HEAD, PUT, MOVE, COPY methods are used + they are extenden with other methods (like PROPFIND for listing directory / metadata fetching) b) WebDAV of course supports TLS/SSL _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
