From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id 44813491DB
	for <ffmpegdev@gitmailbox.com>; Thu,  4 Jul 2024 19:38:56 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 91A9368DAA7;
	Thu,  4 Jul 2024 22:38:54 +0300 (EEST)
Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id C525468DA55
 for <ffmpeg-devel@ffmpeg.org>; Thu,  4 Jul 2024 22:38:47 +0300 (EEST)
X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org )
Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80])
 by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 464Jcl3M025683
 for <ffmpeg-devel@ffmpeg.org>; Thu, 4 Jul 2024 21:38:47 +0200
Received: by phare.normalesup.org (Postfix, from userid 1001)
 id 1DF1A2EFFA; Thu,  4 Jul 2024 21:38:47 +0200 (CEST)
Date: Thu, 4 Jul 2024 21:38:47 +0200
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Message-ID: <Zob6R+owyxShGmi0@phare.normalesup.org>
References: <CAPYw7P5puHdqCeg-_h2WRv6j7tK6tOwk23wcVMZLXU9CetpTcw@mail.gmail.com>
 <b16612a6-5841-43fc-a98d-0fb3a2ff6812@gmail.com>
 <CAPYw7P6HKq7rXz7rTP7M-Y5d8Zm29sixBwKC=WHvTLSCo5BC3A@mail.gmail.com>
 <ZobrHrNYMzXjo5We@phare.normalesup.org>
 <CAPYw7P5vX4xuBq8bzW-jo9oi8y_LptjER7BzVhMvEgZcaBisDw@mail.gmail.com>
 <Zob5FYJk4kx5LuVS@phare.normalesup.org>
 <CAPYw7P4f2a2WUs5oFfyOM4PZ3oUn5ioZ+0zgAP-whTFH8A2nFw@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CAPYw7P4f2a2WUs5oFfyOM4PZ3oUn5ioZ+0zgAP-whTFH8A2nFw@mail.gmail.com>
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (nef.ens.fr [129.199.96.32]); Thu, 04 Jul 2024 21:38:47 +0200 (CEST)
Subject: Re: [FFmpeg-devel] Sorry state of AVOptions
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/Zob6R+owyxShGmi0@phare.normalesup.org/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

Paul B Mahol (12024-07-04):
> Application vendor will issue new free-update with handling for newly
> introduced AVOption type.

So you mean your users have tu update your application to have it handle
new types in more recent FFmpeg?

How do they do if you moved to another project and do not update?

What do they do if in the meantime you raised your prices?

My version is superior: I put the unknown options in a text entry
widget, as text, and they work immediately. If later I update the
application, they will work nice, but they already work now.

This is the kind of thing you have to think about when you design an
API.

-- 
  Nicolas George
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".