Re: HTTP fetching

Joachim> Your package-transport.el looks great; I'll hook it up to Joachim> package-get.el. url.el (from the w3 package) plus some config junk elsewhere in that package is sufficient to get http running, IIRC. Joachim> Concerning my proposal above: It started with a design Joachim> question. Is the transport protocol a property of a Joachim> download site, or an overall property? It's both. The fetch mechanism needs to know what transport to use, obviously, and that varies by site. On the other hand, locally XEmacs doesn't know that FTP is dropped at the firewall until the user expresses a preference. This preference would be implemented as a filter and ordering on URL schema (or whatever our equivalent is going to be). Joachim> I.e., can we assume that _all_ XEmacs mirrors provide at Joachim> least the protocols HTTP and FTP? No, you can't. The mirror list should provide full URLs or equivalent information in an extension of the current format for backward compatibility. Joachim> If not, explaining the package mechanism is a nightmare. Not much we can do about that, as not all mirrors are going to expose the same namespace by ftp and by http even if they do permit both. The best we can do is to hide it by providing full URLs. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.