Re: [vwrap] Technical basis for VW client in a web browser?

Dahlia Trimble <dahliatrimble@gmail.com> Mon, 20 December 2010 00:54 UTC

Return-Path: <dahliatrimble@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BD073A698E for <vwrap@core3.amsl.com>; Sun, 19 Dec 2010 16:54:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X74hOajBdTfD for <vwrap@core3.amsl.com>; Sun, 19 Dec 2010 16:54:48 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by core3.amsl.com (Postfix) with ESMTP id 542013A6989 for <vwrap@ietf.org>; Sun, 19 Dec 2010 16:54:48 -0800 (PST)
Received: by wwi17 with SMTP id 17so2344972wwi.1 for <vwrap@ietf.org>; Sun, 19 Dec 2010 16:56:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=NqezDDqNin/ZdUqPDRXbJ7VAkyKMZvncxb0UA6kT7kc=; b=SSb/8BNPSTfd5elOr4f/cW6PpYuQ5i9IkpRQIEsePTXZmgCWRDMwG2PRugsK25MK+T UE/zSBxUh5t6tom3HAj8nurnHs3l+rjRuGBmkQQ70zWQeDsLZpR7Fjpjoju7k4dmRFaW mkQdPwkFCUNbd/gS2/lo/BzE9pYmSO1H0bWPA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QjaBKlAp0McjK599tpogzT36nnrpWaeu4TsRoinr0FGEKIOjSLCldErhTBU14Knwp7 NTABhXha40PSqFwJAqxeg13tGgeNuxRTxcUCsCs3pVEvdhZoB+Hk0aLEHjveKKg6wsGV h7VGEV1PxsRq/k3U6gsaQi907wItGQbPsii8w=
MIME-Version: 1.0
Received: by 10.216.16.21 with SMTP id g21mr2089191weg.6.1292806599050; Sun, 19 Dec 2010 16:56:39 -0800 (PST)
Received: by 10.216.86.210 with HTTP; Sun, 19 Dec 2010 16:56:39 -0800 (PST)
In-Reply-To: <AANLkTinMstkDv5iq6usxbe1djK7GkPrOAjpKYANyMxcy@mail.gmail.com>
References: <AANLkTintjQdAS=EWfiRu3oWenB42LKsNzJPDJ+5ofBRO@mail.gmail.com> <AANLkTinhWObg6Te2VtGYKXsxBG5=gVDS5szmjtLeOgnm@mail.gmail.com> <AANLkTikYn-iA7osXT_oW8rL61GhK57pp7uJVmTSGVvj7@mail.gmail.com> <AANLkTikFWUxQyT9aNFBk7-Fdb5bNdFT9Bj-dehqVP0WN@mail.gmail.com> <6.2.5.6.2.20101219141829.0a381da8@resistor.net> <AANLkTik-1m=4OOeQN=D3w2t-G-f6DNKwDOmhT5_bNkmb@mail.gmail.com> <AANLkTinMstkDv5iq6usxbe1djK7GkPrOAjpKYANyMxcy@mail.gmail.com>
Date: Sun, 19 Dec 2010 16:56:39 -0800
Message-ID: <AANLkTimHUOwSMCWxAOyMH1O6XwiebOfep2AfN898pETR@mail.gmail.com>
From: Dahlia Trimble <dahliatrimble@gmail.com>
To: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Content-Type: multipart/alternative; boundary=0015176f16f61985860497ccfe42
Cc: vwrap@ietf.org
Subject: Re: [vwrap] Technical basis for VW client in a web browser?
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Dec 2010 00:54:50 -0000

I have used both TCP and UDP in VW applications. I've found that TCP has
acceptable latency and is not really any worse than UDP when either are
tried over a clean, highly functional connection. I've not seen any routers
which drop UDP packets in favor of TCP, and I've not seen any evidence of
better quality TCP connections than UDP in any of my tests. To the contrary,
I've seen UDP perform much better when network conditions are less than
optimal as small messages can be sent immediately and repeated as needed
without waiting for prior message acknowledgement or waiting for a TCP
stream to recover in the event of dropped packets.

TCP seems to be favorable when latency is not critical as it's generally
(but not always) easier to use. UDP seems favorable when latency is critical
as it allows the programmer to control network traffic and tailor it to the
application requirements.

If anyone has any evidence of internet pathways that selectively favor TCP
over other traffic, I'd be interested in seeing it.


On Sun, Dec 19, 2010 at 3:26 PM, Meadhbh Hamrick <ohmeadhbh@gmail.com>wrote;wrote:

> do we really know that UDP is what we want, even for low latency? if you're
> multiplexing messages over a websocket connection, it's highly likely it'll
> be an existing connection (i.e.- it's likely one tcp/ip connection will
> carry several multiplexed websockets messages.)
>
> in my tests, UDP doesn't do much better than TCP if you're near the network
> rate as it seems a lot of routers tend to dump UDP packets first.
>
> most modern OSes now have api calls to let you disable TCP slow-start.
>
> i guess what i'm saying is it might be a good idea to define messages in a
> way so they're transport agnostic. that and I would wager that any latency
> improvements from UDP are dwarfed by latency introduced by application layer
> mechanisms to replace TCP's flow control & resend semantics.
>
> just my $0.02.
> On Dec 19, 2010 2:34 PM, "SM" <sm@resistor.net> wrote:
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
>