<div dir="ltr">What about using WebDAV for HTTP? It supports directory listings (i.e. collections).<br><br><div class="gmail_quote">On Fri, Nov 5, 2010 at 3:35 PM, Troy A. Griffitts <span dir="ltr"><<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
3) The TRANSPORT TECHNOLOGY used to enable this over the Internet.<br>
<br>
We chose FTP because it was more practical. It is very difficult to<br>
implement the programmatic traversal of a directory and file hierarchy<br>
over HTTP. Apache and IIS all spew out different html for directory<br>
listings.<br>
<br>
Now having said this, Nic Carter submitted the first pass at this which<br>
works for our apache server (and likely many apache servers which spew<br>
out the vanilla html index page like here:<br>
<a href="http://crosswire.org/ftpmirror/pub/" target="_blank">http://crosswire.org/ftpmirror/pub/</a><br>
<br>
So, HTTP is currently possible in the engine and if we get push back<br>
from publishers or find users not able to use FTP due to firewall<br>
restrictions, we plan to fully support HTTP moving forward. We simply<br>
need to break out our directory parsing code and make it work well with<br>
a few of the more mainstream httpd services like Apache and IIS.</blockquote></div><br clear="all"><br>-- <br><div dir="ltr">Weston Ruter<br><a href="http://weston.ruter.net/" target="_blank">http://weston.ruter.net/</a><br>
<font size="1"><a href="http://twitter.com/westonruter" target="_blank">@westonruter</a> - <a href="http://www.google.com/profiles/WestonRuter#about" target="_blank">Google Profile</a></font><br></div><br>
</div>