On Wed, Dec 02, 2009 at 10:41:40AM -0800, Junio C Hamano wrote: > Sverre Rabbelier <srabbelier@xxxxxxxxx> writes: > > >> Of course, I never understood why the backend should know the > >> implementation detail that it is based on cURL, so it would be even more > >> modular (at least by my definition) if there was no hard-coded mapping. > > > > Agreed. > > I don't get this point at all. > > Backend is _very_ aware of how it is implemented itself. Naming one > implementation git-remote-http is to declare that "I am the one and only > implementation of http handler" and forces another implementation of http > handler, perhaps based on different toolkit than libcurl, to forever be a > second class citizen that need to use name other than 'http'. At least it can be called as 'foo::http://' (That may be tolerable for alternate implementations but not for primary ones). > The "mapping" you two are calling "hard-coded" may be "hard-coded" but is > a better kind of hard-coding than hard-coding "http" to "this particular > implementation" implicitly like you two seem to be advocating. Think of > it as having one extra layer of indirection. Its already indirected: By filesystem. > When the second implementation of http handler proves to be better than > the current one, we can flip the mapping, and anybody who were using > "http://"; to access some repository will automatically updated to use the > new backend instead of the old one. With your scheme, you probably could > change the name of the old "http" backend to "http-deprecated" and the new > one from "second-class-citizen-http" to "http" to achieve a similar > effect, but I do not think it is as nice as having one extra level of > indirection. The new HTTP support must either be internal or not. And: - If it is internal, renaming can be done anyway. - If it is not, change can not be made. And at package manager level, this is what 'conflicts: ' is about (and alternates of apt). > > However, I am not convinced that we should do any magic to map > > "foo://" to git-remote-foo. On the other hand, I do think it makes > > sense to have something modular that allows "git-remote-http" to be > > implemented as a separate package that can be installed. > > As I said, I do think modular is good, but I think what Dscho is > advocating does not have much to achieve that goal. Why should adding new git native protocol (that doesn't have so special capabilities new core support is fundamentially required) require recompiling git core? Why it should require more than dropping executable handler to suitable place?[*] Why should such protocols need to be specified 'foo::foo://'? Granted, even with current dispatch meachanisms, its possible to hack together something that accepts 'foo:://', 'foo::/' or 'foo::' but that breaks user expectations rather badly (the U in URL stands for 'uniform')... And currently the URL space to be reassigned just produces fatal error messages anyway. [*] Merge strategies have similar issues. IMO, on encountering unknown merge strategy, git merging code should check if there's handler for it, if yes, obtain flags from it and then use it. -Ilari -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html