Re: [mmox] The Structure and Interpretation of LLSD Messages [Was: Re: unefficient binary serialization ?]

Jon Watte <jwatte@gmail.com> Thu, 26 February 2009 04:27 UTC

Return-Path: <jwatte@gmail.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B859E3A6844 for <mmox@core3.amsl.com>; Wed, 25 Feb 2009 20:27:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level:
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599]
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 oY4FvZIjnKHS for <mmox@core3.amsl.com>; Wed, 25 Feb 2009 20:27:21 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by core3.amsl.com (Postfix) with ESMTP id E6F8D3A6B34 for <mmox@ietf.org>; Wed, 25 Feb 2009 20:27:20 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id l9so319856rvb.49 for <mmox@ietf.org>; Wed, 25 Feb 2009 20:27:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=A/1iwdCpkZXqL6+DwE/6VL+JSbJ/tD4ekexz2BLYAp8=; b=Su/HH7isve/VDE38LPwgMWwP4woBMmhgOfkdwNFJKzXcCnmY8psfm5JiZAU+YsLl8X WgcrUuvzj9/uhCitVEMqigF9i5ZdP1m+2gk/khhW4CAhIiaERJoG18CdJ7/9CdPANfVx Yuq14PRk5iKza9wX1Qgn7TzAYOUhavt9V5EvQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=KJSdteJ4jXK9caq8SNf3n0yoSNcr5rrI+sI7lBjjRwUKvkV3sH+7IDe7dLsfuv2BRG dDvF3tzo6L9ayObnqO4If3lvxeNZoB0CTReyj+QaEqKCeSJaQAAz2mqfAy+XAcQBdGOP 4NyfAu0Mqgy99P/c1jjb9uyXidgi+aYUvqMLE=
Received: by 10.141.105.18 with SMTP id h18mr401237rvm.109.1235622461886; Wed, 25 Feb 2009 20:27:41 -0800 (PST)
Received: from ?192.168.1.101? (svn.mindcontrol.org [69.17.45.136]) by mx.google.com with ESMTPS id c20sm507988rvf.1.2009.02.25.20.27.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 25 Feb 2009 20:27:41 -0800 (PST)
Message-ID: <49A61A3C.1090109@gmail.com>
Date: Wed, 25 Feb 2009 20:27:40 -0800
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Morgaine <morgaine.dinova@googlemail.com>
References: <ebe4d1860902241754s7942179ajd4a29dde4e1d1bdb@mail.gmail.com> <49A4A8FA.607@gmail.com> <024355C7-0753-451F-9542-4478D27A2802@lindenlab.com> <e0b04bba0902242245y7ce6cc81i5d67d02b73f65440@mail.gmail.com> <497C7FD9-BF36-458F-98C0-BEECAE611E1A@lindenlab.com> <e17956060902242327x712880c8h184d41dc57dec206@mail.gmail.com> <06CF9E4E-6C20-46CB-B092-68F702C2E185@lindenlab.com> <e17956060902251119w2a02e8f5s4ac686d8a5417b55@mail.gmail.com> <e0b04bba0902251923s34e97186n80f5c2b17294a638@mail.gmail.com>
In-Reply-To: <e0b04bba0902251923s34e97186n80f5c2b17294a638@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org
Subject: Re: [mmox] The Structure and Interpretation of LLSD Messages [Was: Re: unefficient binary serialization ?]
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 04:27:21 -0000

Morgaine wrote:
> While such gateways are fine for non-interactive streaming downloads, 
> unfortunately they introduce latency that can ruin the interactive 
> experience.

In my experience, having done exactly that in some solutions, that 
technical argument doesn't hold water in practice. As long as the 
gateway is close to the source (or destination), and the translator is 
implemented competently, the addition in latency can be fractions of a 
millisecond. Compared to just random noise and jitter from the greater 
Internet, you would be hard pressed to even reliably measure that.

That being said, if someone is proposing the origination of high-volume 
real-time data as XML, then I have to respectfully disagree with the 
proposal on general principle -- for the same reason that we don't try 
to originate, say, streaming video, or telephony voice data as XML. When 
it will generally be transfered binary, you probably want to originate 
it binary, to avoid the dual overhead of first generating XML, and then 
un-generating it again.

Sincerely,

jw