Re: [mmox] RealExtend Teleporting Between Worlds

Jon Watte <jwatte@gmail.com> Thu, 26 February 2009 18:44 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 7B5B328C1DB for <mmox@core3.amsl.com>; Thu, 26 Feb 2009 10:44:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.51
X-Spam-Level:
X-Spam-Status: No, score=-2.51 tagged_above=-999 required=5 tests=[AWL=0.089, 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 ObmwtMomQBz8 for <mmox@core3.amsl.com>; Thu, 26 Feb 2009 10:44:50 -0800 (PST)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by core3.amsl.com (Postfix) with ESMTP id 6F05728C190 for <mmox@ietf.org>; Thu, 26 Feb 2009 10:44:50 -0800 (PST)
Received: by yw-out-2324.google.com with SMTP id 5so859236ywh.49 for <mmox@ietf.org>; Thu, 26 Feb 2009 10:45:11 -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=rIz/iFxCWSsKFDLhU33DxvgEpbH/sQJnV3UgPzwbmZE=; b=FU4/7Htuag6nLrsIGrXnq/cqb+AopWJ7fx/1vE04IFyq2CuMX3e6XFgBNTyjK6bNlc /Y+vdetsUHmdU2oiYuDPrK3khsOmBwTuZ9d1I2hXouDVfbjqSXU2m7NOCErKEO+7KXeE sGU/wXNwlWAMbOeeWXgCC+foxf2vg4BMcqsAY=
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=vMgUXKaIZlIZryTZt8ri6qxgGYnX5DInHf4C531nCyPWF/DhOQT/U0t38bU7bS2JaF Q/mNCnSxpR4p8Wyo+Bdxp6CRDwJUyFd6jPMYDpnG9VZ6aIVn49fLSNyamg00F8P1j2Wf R24OAVhkoFFICrc49k5hkiFQgxq6Yi5WkF6Rg=
Received: by 10.100.42.4 with SMTP id p4mr621065anp.40.1235673911507; Thu, 26 Feb 2009 10:45:11 -0800 (PST)
Received: from ?192.168.168.114? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id c37sm4120076ana.42.2009.02.26.10.45.10 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 26 Feb 2009 10:45:10 -0800 (PST)
Message-ID: <49A6E335.1080009@gmail.com>
Date: Thu, 26 Feb 2009 10:45:09 -0800
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Christian Scholz <cs@comlounge.net>
References: <20090225.182222.10290.1@webmail10.vgs.untd.com> <62BFE5680C037E4DA0B0A08946C0933D502DF61E@rrsmsx506.amr.corp.intel.com> <49A65D92.3060606@comlounge.net>
In-Reply-To: <49A65D92.3060606@comlounge.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] RealExtend Teleporting Between Worlds
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 18:44:51 -0000

Christian Scholz wrote:
> I think requiring having some data in the client will not scale. Why 
> not give it an URL as well and just tell the client to cache it long 
> enough? Should be easy with a REST approach. For SL it might be trees 
> for a game it might in fact be everything if no 

I agree. In interop terms, it will say "the visual presentation of this 
object uses mesh http://www.whatever.com/some-url-here" and you can 
cache that just like you cache other web data.

> A specialized game client could even be so clever as to download it in 
> advance and have some proprietary way of checking whether it's still 
> uptodate or not.

HTTP already has a versioning mechanism. However, for a game with 50,000 
assets, doing 50,000 "HEAD" or "if-modified-since" requests might not 
scale so well ;-)

Sincerely,

jw