Re: [PATCH 18/18] signed push: final protocol update

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 26, 2014, 19:52 UTC
Message-ID: <xmqqa96rhvuh.fsf@gitster.dls.corp.google.com>
In-Reply-To: <xmqqiolfhwhi.fsf@gitster.dls.corp.google.com>

Junio C Hamano <gitster@pobox.com> writes:

> That is unfortunate.  Would it be a major surgery to update the
> protocol not to do that, perhaps by moving the command list from 3
> to 2 (the latter of which is not currently doing anything useful
> payload-wise, other than flushing a HTTP request early)?

Nah, that was one of the most stupid thing I ever said here X. There is nothing that ties #2 and #3 unless the server side keeps some state, so that would not work very well X-<.

Show 6 quoted lines

>
>> Push on smart HTTP is 3 HTTP requests:
>>
>>   1)  get advertisement
>>   2)  POST empty flush packet to tickle auth (literally just "0000").
>>   3)  POST command list + pack

$ 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.