git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git smart protocol via WebSockets - feedback wanted

From
SPStephan Peijnik <stephan@peijnik.at>
Date
Jun 5, 2012, 18:41 UTC
Message-ID
<jqljtk$h6d$1@dough.gmane.org>
In-Reply-To
<7vpq9dobjo.fsf@alter.siamese.dyndns.org>
On 06/05/2012 08:31 PM, Junio C Hamano wrote:
> How does this compare with the smart-http support that tunnels the
> git protocol over http (with some butchering)?

To be honest, I didn't know smart-http support yet. Is that the approach introduced with git 1.6.6?

If so, that approach uses multiple POST requests, meaning multiple TCP and HTTP connections need to be established, multiple requests processed, etc.

The WebSocket approach uses a single HTTP connection which gets upgraded to a WebSocket. This WebSocket then allows the same communication to happen as with the ssh implementation.

So in comparison there is possibly a lot less overhead and, in theory, the performance should be comparable to running the smart protocol over ssh. Personally I'd say the WebSocket approach is cleaner than the HTTP-POST approach.

-- Stephan
Previous: Junio C HamanoNext: Shawn Pearce
Message 3 of 7 in “git smart protocol via WebSockets - feedback wanted”
  1. Stephan PeijnikJun 5, 2012
  2. Junio C HamanoJun 5, 2012
  3. Stephan PeijnikJun 5, 2012
  4. Shawn PearceJun 5, 2012
  5. Stephan PeijnikJun 5, 2012
  6. Shawn PearceJun 5, 2012
  7. Shawn PearceJun 5, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.