On Mon, 3 Apr 2017 11:25:39 +0200 Michael Niedermayer <mich...@niedermayer.cc> wrote:
> On Mon, Apr 03, 2017 at 07:10:42PM +1000, Timothy Lee wrote: > > On 04/03/2017 06:35 PM, Nicolas George wrote: > > >Hi. Thanks for the patch. > > > > > >Le quartidi 14 germinal, an CCXXV, Timothy Lee a écrit : > > >>Capture is an input stream capture protocol that dumps the input stream > > >>to a > > >>file. The default name of the output file is "capture.dat", but it can be > > >>changed using the "capture_file" option. > > >> > > >>capture.c borrows heavily from cache.c. > > >Can you explain more precisely how and why? Borrowing code often means > > >features could be merged or should be more clearly separated, depending > > >on cases. > > > > Hi Nicolas, > > > > Thanks for your quick reply. Regarding the almost direct copy of > > code from cache.c, I previously submitted a patch on 31 March that > > adds a "cache_file" option to the cache protocol. It was intended > > to allow a specifically named cache file to serve as a dump of the > > input stream. > > > > Michael Niedermayer explained that his intention was to maintain a > > caching system that was more consistent with how a browser's cache > > works, and my changes to the cache protocol was not appropriate. > > both can be done in cache. > the primary way of caching in cache.c should be automatic though > and not require the user to manually set it up per url I don't think disk cache management should be in the scope of FFmpeg. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
