Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion General purpose P2P API?

Received: by 10.50.185.202 with SMTP id fe10mr956524igc.3.1326950120176;
        Wed, 18 Jan 2012 21:15:20 -0800 (PST)
X-BeenThere: discuss-webrtc@googlegroups.com
Received: by 10.50.216.230 with SMTP id ot6ls20094829igc.3.gmail; Wed, 18 Jan
 2012 21:15:18 -0800 (PST)
Received: by 10.50.209.99 with SMTP id ml3mr955544igc.3.1326950118527;
        Wed, 18 Jan 2012 21:15:18 -0800 (PST)
Received: by 10.50.209.99 with SMTP id ml3mr955542igc.3.1326950118513;
        Wed, 18 Jan 2012 21:15:18 -0800 (PST)
Return-Path: <jube...@google.com>
Received: from mail-iy0-f173.google.com (mail-iy0-f173.google.com [209.85.210.173])
        by gmr-mx.google.com with ESMTPS id at5si5543092igc.0.2012.01.18.21.15.18
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 18 Jan 2012 21:15:18 -0800 (PST)
Received-SPF: pass (google.com: domain of jube...@google.com designates 209.85.210.173 as permitted sender) client-ip=209.85.210.173;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jube...@google.com designates 209.85.210.173 as permitted sender) smtp.mail=jube...@google.com; dkim=pass header...@google.com
Received: by iaeo4 with SMTP id o4so14555371iae.18
        for <discuss-webrtc@googlegroups.com>; Wed, 18 Jan 2012 21:15:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :x-system-of-record:content-type;
        bh=Jr4MZjHsKWGs4QRKGRX5HELGbgMhJ5pgytKR3jZJAeQ=;
        b=HCZ77KMkKreaSPBseQhFryPOrxEUsLfk1Tn8WQ1PFrczHurqJqCVLzuYocHnLtbLYe
         3p4pqw6mBbpEq2mJ0pOG6fCuqy/zc+/UD1DVu7ZD2OKzjeHqBVJcX7WQWFvFe/IGGrSQ
         rWX5JnVB/9pO2qJy3Ceq3KZbtz8kp2FXLxzzI=
Received: by 10.42.168.138 with SMTP id w10mr20591244icy.47.1326950118408;
        Wed, 18 Jan 2012 21:15:18 -0800 (PST)
Received: by 10.42.168.138 with SMTP id w10mr20591238icy.47.1326950118341;
 Wed, 18 Jan 2012 21:15:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.85.132 with HTTP; Wed, 18 Jan 2012 21:14:57 -0800 (PST)
In-Reply-To: <19918303.2150.1326949679959.JavaMail.geo-discussion-forums@prhu31>
References: <26783210.171.1326940404074.JavaMail.geo-discussion-forums@prog27>
 <4F178E90.6070...@jesup.org> <CAOJ7v-3xRpiFsiEapgXp4n2aoybxsiyApK9rNAGoOxQo0xX...@mail.gmail.com>
 <19918303.2150.1326949679959.JavaMail.geo-discussion-forums@prhu31>
From: Justin Uberti <jube...@google.com>
Date: Thu, 19 Jan 2012 00:14:57 -0500
Message-ID: <CAOJ7v-2x24JEOw8ofXtV0SSWPViSnp7RTPMFm1dg5gpfnfA...@mail.gmail.com>
Subject: Re: General purpose P2P API?
To: discuss-webrtc@googlegroups.com
X-System-Of-Record: true
Content-Type: multipart/alternative; boundary=90e6ba6e8e12703b3104b6daa63d

--90e6ba6e8e12703b3104b6daa63d
Content-Type: text/plain; charset=UTF-8

Correct. Although, for text chat, you might as well use WebSockets.

On Thu, Jan 19, 2012 at 12:07 AM, Dan Fabulich <danfabul...@gmail.com>wrote:

> Thanks. To clarify, does that mean that it's not currently possible to
> build a P2P text chat client in the Chrome dev channel implementation?

--90e6ba6e8e12703b3104b6daa63d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Correct. Although, for text chat, you might as well use WebSockets.<br><br>=
<div class=3D"gmail_quote">On Thu, Jan 19, 2012 at 12:07 AM, Dan Fabulich <=
span dir=3D"ltr">&lt;<a href=3D"mailto:danfabul...@gmail.com">danfabulich@g=
mail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Thanks. To clarify, does that mean that it&#=
39;s not currently possible to build a P2P text chat client in the Chrome d=
ev channel implementation?</blockquote>

</div><br>

--90e6ba6e8e12703b3104b6daa63d--