On Tue, Feb 23, 2016 at 03:32:02AM +0100, Jason A. Donenfeld wrote: > In case anyone else finds this useful, I wrote this: > > https://git.zx2c4.com/git-daemon-dummy/about/ > > It's an epoll-based responder for git:// that simply returns an error > telling users of a new URI. Neat. > The purpose is to phase out git-daemon in > favor of more secure TLS/HTTPS endpoints. With HTTPS certificates now > being free, seems like this could be useful. Yeah, the existence of HTTPS (and the fact that the same URL can be both anonymous and authenticated) is nice. Unfortunately, git-over-https is not as efficient as the other protocols, because it's not asynchronously bi-directional. It would probably be relatively simple to make a "gits://" protocol, but I think it would be more interesting still if we could do git-over-websockets, to get the ubiquity benefits of HTTP. I looked into it once, but was unable to find any reasonably sized explanation of how to implement either the server or client side of websockets. :) > My personal motivation is that I'd like to just totally kill the > git-daemon service, but somebody hard coded a URI of mine into a real > printed textbook [1], so I don't want it to go stale suddenly. So, I > need some way of informing users of the new URI. Darn printed books. I thought the Ministry of Truth was supposed to take care of keeping our facts up to date. -Peff -- 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