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

Re: Git Daemon Dummy: 301 Redirects for git:// to https://

From
Duy Nguyen <pclouds@gmail.com>
Date
Feb 23, 2016, 12:13 UTC
Message-ID
<CACsJy8D1H6k2FJOHQnT3BEnpXDPn8+ux-vJfDLMhO-JybFvR=w@mail.gmail.com>
In-Reply-To
<20160223061517.GA3252@sigill.intra.peff.net>
On Tue, Feb 23, 2016 at 1:15 PM, Jeff King <peff@peff.net> wrote:
> 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. :)

Wikipedia explained handshake in four paragraphs. Then you only have to chew about ten pages of RFC6455, from page 27 to master data frames (and we probably just need binary frames for pkt-line, or fragmented when sending the pack). Come on, give us git+ws:// :D

PS. Too bad I couldn't find any minimal library that just deals with websocket data frame handling. I suppose curl can deal with handshake just fine.

-- 
Duy
Previous: Jeff KingNext: Jason A. Donenfeld
Message 3 of 7 in “Git Daemon Dummy: 301 Redirects for git:// to https://”
  1. Jason A. DonenfeldFeb 23, 2016
  2. Jeff KingFeb 23, 2016
  3. Duy NguyenFeb 23, 2016
  4. Jason A. DonenfeldFeb 23, 2016
  5. Jason A. DonenfeldFeb 23, 2016
  6. John KeepingFeb 23, 2016
  7. Jason A. DonenfeldFeb 23, 2016

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.