Re: [rtcweb] URIs for rtcweb "calls"

"Timothy B. Terriberry" <> Sun, 14 August 2011 11:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CA9D521F886D for <>; Sun, 14 Aug 2011 04:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eWwmQ3t0kbYr for <>; Sun, 14 Aug 2011 04:45:47 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 25AD321F8853 for <>; Sun, 14 Aug 2011 04:45:46 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAN60R06sGgRa/2dsb2JhbABBpxKBXYFAAQEEAThAAQULCyEWDwkDAgECAUUTAQcCh2yyG4ZHBIdfkDAPjAk
X-IronPort-AV: E=Sophos;i="4.67,368,1309752000"; d="scan'208";a="202768925"
Received: from (HELO ([]) by with ESMTP; 14 Aug 2011 07:46:26 -0400
X-UNC-Auth-As: tterribe
Received: from [] ( []) (authenticated bits=0) by (8.14.4/8.14.3) with ESMTP id p7EBjsop026859 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <>; Sun, 14 Aug 2011 07:46:05 -0400 (EDT)
Message-ID: <>
Date: Sun, 14 Aug 2011 04:45:39 -0700
From: "Timothy B. Terriberry" <>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101120 Gentoo/2.0.10 SeaMonkey/2.0.10
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] URIs for rtcweb "calls"
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 14 Aug 2011 11:45:47 -0000

> rtc-web context.  That would still fire up the full game context,
> slotting the user into the game (rather than making a phone call).

By "full game context" do you mean it would somehow load an http webpage 
with HTML+CSS+JS to handle the signaling? If that's the case, what 
advantages does this offer over normal http[s] URLs (with a path to the 
necessary page and parameters, etc. needed to carry sufficient 
information to establish the session). That certainly seems to already 
cover the case of, "A URI that I could use to paste into a chat window." 
How does it handle all the things that an http[s] URL already provides 
(port, path, caching, proxies, all the associated services built around 
http (e.g., etc.)?

If that's not the case, what do you mean by "context"?