On 6/23/2015 12:46 AM, Reynaldo H. Verdejo Pinochet wrote: > Not really getting into the whole discussion on blocking > remarks to a running (sponsored) project. I sincerely hope > we all agree that once work has started on these, we should > try to be constructive and let the student do their job while > benefiting from all we can feed to them on the do-it-better > side.
As noted in my other mail(s), I agree, since work has started already on GSOC. > I do understand resource renaming and removing are borderline > use cases, but I also see the need for such functionality when, for > instance, there's no easy way to properly inform the application > about what and how to rename/move. It been a protocol:// issue, > a loosely defined naming%0Xd*.ext convention, etc (there are > similar examples for renaming). Lacking a better solution and > considering we should be at least responsible for our own cleanup, > I'd just make sure this API stays in the avpriv_ realm and work > together on designing a solution that would let us have this > functionality available for internal use while being maintainable > , have good platform coverage, and be as uncluttered (use-case wise) > as it can possibly be. That's the most reasonable thing I've read so far. - Derek _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
