On Tue, Jan 07, 2014 at 03:18:43AM +0100, Martin Bähr wrote: > ftp is a protocol of the past that deserves to die. any mirror service > should at least be able to give http access. > > conary is accessed via http. so it should be possible to use services > like claudflare or similar. distributing http over multiple machines is > not exactly dificult.
No, Conary runs by speaking XML-RPC over HTTP to a web service. "Web mirror" services are just HTTP access to static resources. Conary does work correctly through an HTTP proxy but there's not much value in that. While Conary's *architecture* is in general very resource-oriented, its protocol implementation is not RESTful. > if redirects work, distributing requests over multiple conary repos > should be no problem. That isn't true, because the server side creates changesets based on requests. So it doesn't round-robin very well... > how does the file access work? > but can file downloads be redirected to "dumb" http fileservers? For years, we talked about ways that we could extend Conary that would make this useful, but none of them has been completely obvious. Even a caching Conary proxy is an XML-RPC web service. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
