Re: [rtcweb] WebRTC endpoint non-browser

Lorenzo Miniero <lorenzo@meetecho.com> Mon, 08 December 2014 17:26 UTC

Return-Path: <lorenzo@meetecho.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 484111AC3F2 for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 09:26:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.281
X-Spam-Level:
X-Spam-Status: No, score=0.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXy1JQOlzeZZ for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 09:26:21 -0800 (PST)
Received: from smtpcmd02102.aruba.it (smtpcmd02102.aruba.it [62.149.158.102]) by ietfa.amsl.com (Postfix) with ESMTP id CBF2D1ACCDA for <rtcweb@ietf.org>; Mon, 8 Dec 2014 09:26:20 -0800 (PST)
Received: from android-8f633aaf6de55e4c ([79.9.157.122]) by smtpcmd02.ad.aruba.it with bizsmtp id R5Rt1p00B2ejfy7015S9fF; Mon, 08 Dec 2014 18:26:19 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <92D0D52F3A63344CA478CF12DB0648AADF35B343@XMB111CNC.rim.net>
References: <92D0D52F3A63344CA478CF12DB0648AADF35B076@XMB111CNC.rim.net> <5485CD70.4010605@gmail.com> <92D0D52F3A63344CA478CF12DB0648AADF35B132@XMB111CNC.rim.net> <CALiegfkJXcF-_YAYWxxZ44peo1uiV49fsvMpgjeWRSA20FG-Uw@mail.gmail.com> <92D0D52F3A63344CA478CF12DB0648AADF35B343@XMB111CNC.rim.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----F6B8J8IZ5K6SXQY4ZPFM999BYKXL1J"
Content-Transfer-Encoding: 8bit
From: Lorenzo Miniero <lorenzo@meetecho.com>
Date: Mon, 08 Dec 2014 18:25:44 +0100
To: Gaelle Martin-Cocher <gmartincocher@blackberry.com>, =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Message-ID: <9EE9BFFF-9C24-4FA2-96BB-41D5363F6006@meetecho.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/_TkXYvl_QCQ3IgjP17TV6Qtj65g
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] WebRTC endpoint non-browser
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 08 Dec 2014 17:26:23 -0000

Many of us are,

L.

Il 08 dicembre 2014 18:24:25 CET, Gaelle Martin-Cocher <gmartincocher@blackberry.com> ha scritto:
>Are you building such app?
>
>-----Original Message-----
>From: Iñaki Baz Castillo [mailto:ibc@aliax.net] 
>Sent: Monday, December 08, 2014 12:23 PM
>To: Gaelle Martin-Cocher
>Cc: Sergio Garcia Murillo; rtcweb@ietf.org
>Subject: Re: [rtcweb] WebRTC endpoint non-browser
>
>2014-12-08 17:24 GMT+01:00 Gaelle Martin-Cocher
><gmartincocher@blackberry.com>y.com>:
>> You are listing webrtc-compatible endpoints, not webrtc “non browser”
>> endpoints.
>>
>> I am not asking of generic types of services but who actually belong 
>> to the non browser endpoint category.
>
>If you build a mobile native app with WebRTC capabilities (using a
>WebRTC library or your own one) then that is a "non browser" WebRTC
>endpoint.
>
>
>
>--
>Iñaki Baz Castillo
><ibc@aliax.net>
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb

-- 
Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità.