On Thu, Mar 11 2021, Emily Shaffer wrote: > On the frontend, this is supported by asking for a file path, rather > than by reading stdin. Reading directly from stdin would involve caching > the entire stdin (to memory or to disk) and reading it back from the > beginning to each hook. We'd want to support cases like insufficient > memory or storage for the file. While this may prove useful later, for > now the path of least resistance is to just ask the user to make this > interim file themselves. We need to worry about cases where we wouldn't have enough memory to buffer the stdin, but still need to then do repo operations on the input from such a file, presumably some giant pre-receive update or something. Seems unlikely, and the convenience of having stdin just work by just allocating that seems appealing, but let's read on to the rest of the series...
