[sword-devel] HTTP Transport support (was: Remote Module Repository Wiki)
Troy A. Griffitts
scribe at crosswire.org
Fri Nov 5 08:25:07 MST 2010
Thanks for the suggestion Weston,
I had no idea WebDAV allowed programmatic traversal of remote content.
That's great to know!
I wonder at the value of depending on WebDAV to solve our problem though.
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.
On 11/05/2010 02:45 PM, Weston Ruter wrote:
> What about using WebDAV for HTTP? It supports directory listings (i.e.
> On Fri, Nov 5, 2010 at 3:35 PM, Troy A. Griffitts <scribe at crosswire.org
> <mailto:scribe at crosswire.org>> wrote:
> 3) The TRANSPORT TECHNOLOGY used to enable this over the Internet.
> We chose FTP because it was more practical. It is very difficult to
> implement the programmatic traversal of a directory and file hierarchy
> over HTTP. Apache and IIS all spew out different html for directory
> Now having said this, Nic Carter submitted the first pass at this which
> works for our apache server (and likely many apache servers which spew
> out the vanilla html index page like here:
> So, HTTP is currently possible in the engine and if we get push back
> from publishers or find users not able to use FTP due to firewall
> restrictions, we plan to fully support HTTP moving forward. We simply
> need to break out our directory parsing code and make it work well with
> a few of the more mainstream httpd services like Apache and IIS.
> Weston Ruter
> @westonruter <http://twitter.com/westonruter> - Google Profile
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel