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

Re: More on git over HTTP POST

From
Shawn O. Pearce <spearce@spearce.org>
Date
Aug 3, 2008, 04:10 UTC
Message-ID
<20080803041014.GD27465@spearce.org>
In-Reply-To
<48952A62.6050709@zytor.com>
"H. Peter Anvin" <hpa@zytor.com> wrote:
Show 5 quoted lines
> Junio C Hamano wrote:
>>  For example, putting them [capabilities] on extra HTTP headers is probably Ok.
>
> I think that would be a mistake, just because it's one more thing for  
> proxies to screw up on.

I didn't realize we were in an era of proxies that are that brain-damaged that they cannot relay the other headers. The Amazon S3 service relies heavily upon their own extended headers to make their REST API work. If proxies stripped that stuff out then the client wouldn't work at all.

IOW I had thought we were past this dark age of the Internet.
> It's better to have negotiation information in  
> the payload, before the "real" data.
I guess I could do that.  At least for the really complex stuff.
> Obviously one thing that needs to be included in each transaction is a  
> transaction ID that will be reported back on the next transaction, since  
> you can't rely on a persistent connection.

No. That requires the server to maintain state. We don't want to do that if we can avoid it. I would much rather have the clients handle the state management as it simplifies the server side, especially when you start talking about reverse proxies and/or load-balancers running in front of the server farm.

-- 
Shawn.
Previous: H. Peter AnvinNext: david@lang.hm
Message 11 of 40 in “More on git over HTTP POST”
  1. H. Peter AnvinAug 1, 2008
  2. Shawn O. PearceAug 2, 2008
  3. Daniel StenbergAug 2, 2008
  4. Shawn O. PearceAug 2, 2008
  5. Petr BaudisAug 2, 2008
  6. Shawn O. PearceAug 2, 2008
  7. Shawn O. PearceAug 3, 2008
  8. Junio C HamanoAug 3, 2008
  9. Shawn O. PearceAug 3, 2008
  10. H. Peter AnvinAug 3, 2008
  11. Shawn O. PearceAug 3, 2008
  12. david@lang.hmAug 3, 2008
  13. H. Peter AnvinAug 3, 2008
  14. H. Peter AnvinAug 3, 2008
  15. H. Peter AnvinAug 3, 2008
  16. Shawn O. PearceAug 3, 2008
  17. H. Peter AnvinAug 3, 2008
  18. H. Peter AnvinAug 3, 2008
  19. Mike HommeyAug 3, 2008
  20. 1/2 Add backdoor options to receive-pack for use in Git-aware CGIShawn O. Pearce, Aug 3, 2008
  21. 2/2 Add Git-aware CGI for Git-aware smart HTTP transportShawn O. Pearce, Aug 3, 2008
  22. H. Peter AnvinAug 3, 2008
  23. Shawn O. PearceAug 3, 2008
  24. Junio C HamanoAug 3, 2008
  25. Shawn O. PearceAug 4, 2008
  26. Rogan DawesAug 4, 2008
  27. Johannes SchindelinAug 4, 2008
  28. Rogan DawesAug 4, 2008
  29. Johannes SchindelinAug 4, 2008
  30. Shawn O. PearceAug 4, 2008
  31. Rogan DawesAug 4, 2008
  32. Shawn O. PearceAug 4, 2008
  33. Rogan DawesAug 4, 2008
  34. H. Peter AnvinAug 5, 2008
  35. Shawn O. PearceAug 5, 2008
  36. H. Peter AnvinAug 5, 2008
  37. Shawn O. PearceAug 5, 2008
  38. H. Peter AnvinAug 5, 2008
  39. Add Git-aware CGI for Git-aware smart HTTP transportH. Peter Anvin, Aug 13, 2008
  40. Shawn O. PearceAug 13, 2008

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.