Re: [RFC PATCH v3 00/17] Return of smart HTTP
- From
- Marcus Camen <mcamen@mcamen.de>
- Date
- Oct 22, 2009, 19:48 UTC
- Message-ID
- <200910222148.31016.mcamen@mcamen.de>
- In-Reply-To
- <ca433830910161604g5a6bde76n26eb2b1e8155fb36@mail.gmail.com>
On Samstag 17 Oktober 2009, Mark Lodato wrote:
Show 10 quoted lines
> I just realized I forgot to say something in my last email: THANK > YOU!!! I have been looking forward to this for a long time. I was > planning to one day to sit down and start thinking about how to > implement a smart protocol, and then I see a post saying that not only > has someone figured out the protocol, but he has implemented it! > Amazing! This is really crucial for corporate adoption, at least at > my job. We need to have strong authentication for many users, and the > SSH key management is just a nightmare, not to mention that not all > users can SSH due to firewalls. This will save me so much time and > frustration. Thanks!
As I am using git in a corporate environment I couldn't agree more. smart- http definitely is the most import addition to git in the last months.
So far I didn't carry out extensive production runs but my first tests already showed that the smart-http backend solves many problems we have with the dumb webdav approach (no hooks, insane amount of http requests, slow performance, ...).
As I have a systems engineer (not a C coder) perspective on git I cannot comment an any possible glitches of this implementation. I just want to make sure that everyone recognizes just how import smart-http is for corporate environments and that the current patch already solves a lot of problems.
Regards, Marcus