From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id AB5D543F03 for ; Thu, 18 Aug 2022 08:48:15 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id D8B7568B9B9; Thu, 18 Aug 2022 11:48:13 +0300 (EEST) Received: from mail.acc.umu.se (mail.acc.umu.se [130.239.18.156]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 4F3BF68B98F for ; Thu, 18 Aug 2022 11:48:07 +0300 (EEST) Received: from localhost (localhost.localdomain [127.0.0.1]) by amavisd-new (Postfix) with ESMTP id B3BEF44B90 for ; Thu, 18 Aug 2022 10:48:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=acc.umu.se; s=mail1; t=1660812486; bh=+QIMsovchAA+DZ+gePC57wzf0l2w2/1vfhWHKQdbRd0=; h=Subject:From:To:Date:In-Reply-To:References:From; b=MTeMqQiiZIbGRC+sUk1FHJ6AoumjDdq4FCmYSOy2o/h2PUdjb3QMP/5adKKy1/Y23 7GWIwJ/+B8i9F1kz6BNeZyc53N/jlumWX9EBHaCJH/m/740cPgR0EL/3OBdKAV5UXH perZTBl+mzhDanPBJG6CyKDpKU/HompUZ66DMKWVIngetiuq/D2OBYRVsNaeE1lLno 9Hnsaw5VP3SkELXiBmXezpzG4W94dgCXiucHvLMtby9SbAVmGDNkPNXX64QZjJAqxv S2OQwibg/D3KlPm7LeMwR8rVBk93r4pO1ucEnLd/R8ZgeTN2Pz5Ng52zpRw9HL3N8/ r44wkr/r2+xvA== Received: from [192.168.1.101] (m5-243-138-196.cust.tele2.se [5.243.138.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: tjoppen) by mail.acc.umu.se (Postfix) with ESMTPSA id 0FA3144B8F for ; Thu, 18 Aug 2022 10:48:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=acc.umu.se; s=mail1; t=1660812486; bh=+QIMsovchAA+DZ+gePC57wzf0l2w2/1vfhWHKQdbRd0=; h=Subject:From:To:Date:In-Reply-To:References:From; b=MTeMqQiiZIbGRC+sUk1FHJ6AoumjDdq4FCmYSOy2o/h2PUdjb3QMP/5adKKy1/Y23 7GWIwJ/+B8i9F1kz6BNeZyc53N/jlumWX9EBHaCJH/m/740cPgR0EL/3OBdKAV5UXH perZTBl+mzhDanPBJG6CyKDpKU/HompUZ66DMKWVIngetiuq/D2OBYRVsNaeE1lLno 9Hnsaw5VP3SkELXiBmXezpzG4W94dgCXiucHvLMtby9SbAVmGDNkPNXX64QZjJAqxv S2OQwibg/D3KlPm7LeMwR8rVBk93r4pO1ucEnLd/R8ZgeTN2Pz5Ng52zpRw9HL3N8/ r44wkr/r2+xvA== Message-ID: From: Tomas =?ISO-8859-1?Q?H=E4rdin?= To: FFmpeg development discussions and patches Date: Thu, 18 Aug 2022 10:48:04 +0200 In-Reply-To: <20220817172145.GD2088045@pb2> References: <20220817172145.GD2088045@pb2> User-Agent: Evolution 3.38.3-1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] API enhancements / broken promises X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: ons 2022-08-17 klockan 19:21 +0200 skrev Michael Niedermayer: > > Now to achieve this do we need xml and json ? > grep tells me we have 500 matches (not counting docs) for xml and > almost 100 > for json > Also for streaming and some cases filtering being able to serialize > objects > would be useful. xml and json seem better choices than some ad-hoc > format > So i would awnser the question do we need XML and JSON, with yes we > live > in a world that uses XML and JSON so if we give the option to use it > too > that makes it easier for others to interact. > > now do we need our own implementation of it ? I dont know but we have > in almost all cases favored our native implementations when someone > wrote > one. And libxml2 has had so many security issues that i think we > should > at least consider replacing it. Absolutely not. The solution is to fix and improve libxml2, not to add to the problem with our own XML parser which will inevitably have its own set of bugs. NIH for its own sake does nothing but split developer effort and increase the number of bugs. Parsing is hard and the source of the vast majority of CVEs. This project should take the advice of the langsec community to heart. Resist the urge to write your own shotgun parsers because it is "fun". Make your protocol context-free or regular! /Tomas _______________________________________________ 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".