Re: [rtcweb] Platforms that support H264

cowwoc <cowwoc@bbs.darktech.org> Mon, 04 November 2013 14:18 UTC

Return-Path: <cowwoc@bbs.darktech.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0EC111E82E2 for <rtcweb@ietfa.amsl.com>; Mon, 4 Nov 2013 06:18:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.765
X-Spam-Level:
X-Spam-Status: No, score=-4.765 tagged_above=-999 required=5 tests=[AWL=-1.166, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gqMxktfJ2QJs for <rtcweb@ietfa.amsl.com>; Mon, 4 Nov 2013 06:18:26 -0800 (PST)
Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) by ietfa.amsl.com (Postfix) with ESMTP id 5480A11E82E4 for <rtcweb@ietf.org>; Mon, 4 Nov 2013 06:18:19 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id u16so12283434iet.18 for <rtcweb@ietf.org>; Mon, 04 Nov 2013 06:18:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=YPFFuM9kj0Q50ANhXBhAAzeLNdCxMDNd4sOtW4LScfg=; b=OiuhSpcpIBZu1UrzqBKSCYD7SvnEWIeOuADHHDpeLIBuqjJmle64Pux9W5VGxYq9xJ 0YOIfJ9aNpv5YfILV/nZdKLySXESxGasZdNFYZAjBc5LE1QE8SOik9dDLUCANoy1jTUm TS46e1k9p4cL//hOWofanf3/mbbd5EBhYudAitwyOydN2nhRHgauNM3N+gg/qlK420Ke HQBSn+37hlAe/0TvVxhzEPq/XlE3Puld6s4OBBcLQnaSjnH4zXyUimKC9eu7kmx3k3TY Rmd0w6NzO1u2zSj1RjnwSOR/KeWw1r/PLa+hMCGJU/V3Tz+UiC1jDXLxa80o2ykY0uDf iBBw==
X-Gm-Message-State: ALoCoQmXYg1SsyDqJlalkpk5KxG/ptdbKtngC92AY6dinksCF238vct1HbwytdcO08DfHiJ8p7l0
X-Received: by 10.50.16.68 with SMTP id e4mr11940188igd.12.1383574698593; Mon, 04 Nov 2013 06:18:18 -0800 (PST)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id y10sm2166205igl.4.2013.11.04.06.18.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Nov 2013 06:18:17 -0800 (PST)
Message-ID: <5277ACA8.8030008@bbs.darktech.org>
Date: Mon, 04 Nov 2013 09:18:16 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: David Singer <singer@apple.com>
References: <CAOqqYVEER_HprgauRawO+_gGdLdMY1MUY8jrMhhi3yVDL31bFg@mail.gmail.com> <52740478.6030109@nostrum.com> <CAOJ7v-2+_4QZwc8vEtdwVDWSP-d-z+ggB0u+VM6WnA=f-k4-XA@mail.gmail.com> <BLU404-EAS261C783EDA4575EE1A7E53593F40@phx.gbl> <52750E3C.9060206@bbs.darktech.org> <CABkgnnVR9=oWVzRaRuD701tvZCtp+SO1n6c65hJELLVfB8QcOA@mail.gmail.com> <C21C6AC2-29F8-4DFF-BB48-5E3D625DCD65@phonefromhere.com> <CAPvvaaK-bKt-zDEq2qibRrm51VbRGAV=95JShKFdCpJszw5Tww@mail.gmail.com> <1383413266.41025.YahooMailNeo@web171304.mail.ir2.yahoo.com> <5275395B.5060709@bbs.darktech.org> <7208CC8D-1F25-43A7-A887-C85D3B18363E@apple.com> <5277A8E8.2000004@bbs.darktech.org> <6CA57EC6-2CFD-4527-9A83-5647DB474144@apple.com>
In-Reply-To: <6CA57EC6-2CFD-4527-9A83-5647DB474144@apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Platforms that support H264
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2013 14:18:34 -0000

On 04/11/2013 9:12 AM, David Singer wrote:
> No, it really isn't. There is a world of difference between 
> implementing something and making an API to it public or available. 
> Good grief. 

Yes, yes, obviously... but my point was that there is a huge hump even 
after you publish the API. There is still a long ramp-up time until that 
API becomes publicly available, garners sufficient market-share and is 
proven to have the necessary stability for production use. We're talking 
about what exists *today*, not a few months in the future. Today, iOS 
does not have real-time H.264 support.

Gili