Re: [rtcweb] Facebook is not SIP

Neil Stratford <neils@belltower.co.uk> Thu, 20 October 2011 09:36 UTC

Return-Path: <neils@vipadia.com>
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 7165C21F8B1E for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 02:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.961
X-Spam-Level:
X-Spam-Status: No, score=-2.961 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 Zu-nEmInHEjc for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 02:36:15 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id B775821F8B17 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 02:36:15 -0700 (PDT)
Received: by iabn5 with SMTP id n5so3566821iab.31 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 02:36:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.3.225 with SMTP id 33mr3985317ibo.87.1319103375095; Thu, 20 Oct 2011 02:36:15 -0700 (PDT)
Sender: neils@vipadia.com
Received: by 10.231.199.4 with HTTP; Thu, 20 Oct 2011 02:36:15 -0700 (PDT)
In-Reply-To: <4E9FEA28.10900@alvestrand.no>
References: <CALiegfmWebR6pJCpCYhH3YWNTqnfENXU_uiu1Db5joM-RSrVAQ@mail.gmail.com> <4E9FEA28.10900@alvestrand.no>
Date: Thu, 20 Oct 2011 10:36:15 +0100
X-Google-Sender-Auth: U76DTpzo8Lezz1gb9m--RFgMkIA
Message-ID: <CABRok6=NBiZoJQ5aAFsMO3kSumHLV-7NfvQgH2nWEZTB-1uh7Q@mail.gmail.com>
From: Neil Stratford <neils@belltower.co.uk>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary=00151773de8e18364b04afb7b0c4
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Facebook is not SIP
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: Thu, 20 Oct 2011 09:36:16 -0000

On Thu, Oct 20, 2011 at 10:30 AM, Harald Alvestrand <harald@alvestrand.no>wrote:

> On 10/20/11 11:23, Iñaki Baz Castillo wrote:
>
>> Hi all,
>>
>> When two Facebook users chat via web, they are already using a
>> signaling protocol in-the-wire, which one? The *custom* signaling
>> protocol Facebook designed.
>>
> They're using XMPP: https://developers.facebook.**com/docs/chat/<https://developers.facebook.com/docs/chat/>
>

I believe that is just for interop with external applications and not used
by their own web applications, though I may be wrong.

http://www.erlang-factory.com/upload/presentations/31/EugeneLetuchy-ErlangatFacebook.pdfis
an interesting read.

Neil