Re: [mmox] User Accounts / "Object" Transfer.

Jon Watte <jwatte@gmail.com> Thu, 19 February 2009 00:37 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 EDDC73A6A13 for <mmox@core3.amsl.com>; Wed, 18 Feb 2009 16:37:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.412
X-Spam-Level:
X-Spam-Status: No, score=-2.412 tagged_above=-999 required=5 tests=[AWL=0.187, 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 s-OaPO3qDMLw for <mmox@core3.amsl.com>; Wed, 18 Feb 2009 16:37:06 -0800 (PST)
Received: from mail-qy0-f11.google.com (mail-qy0-f11.google.com [209.85.221.11]) by core3.amsl.com (Postfix) with ESMTP id 0C7A73A693C for <mmox@ietf.org>; Wed, 18 Feb 2009 16:37:05 -0800 (PST)
Received: by qyk4 with SMTP id 4so321720qyk.13 for <mmox@ietf.org>; Wed, 18 Feb 2009 16:37:17 -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:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=vX0g+iYy6yst9ET4p7KfuyA4D8MPOQAFsluwrP+9AwM=; b=Azw+6spZdlWObvsxOHQrEDuNmRlO1+AbIuaAiuKgi8j9Jxa6lh8/ZyeF0r4eYYIfSD 2KNawnFRX3u4scNJjd2YA4mjHNsD4vl5gsyhXn3cE6fnbkA5q9D511RGhf2vcwlI+ck6 +1tg3w6pFqbR3eb2qSMlueJRzYmealbzw/aJk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=wJY8+j9TOmfoU0ye1fZ73Sm0RFj2nYKOWPxBO57oVsWlNVTa1HN8OCr3i1sd0sJXcZ 6fQEsWWoVwIYxlG7+m7JU/NBmvGBXZugiHwQbmPH9adYuqhJFRRQ2GmIm14FsHLiukYL MS2Xua9RzheMNWjdO6aAeJ8IU+Topos64w9Sk=
Received: by 10.224.53.203 with SMTP id n11mr12076670qag.192.1235003837686; Wed, 18 Feb 2009 16:37:17 -0800 (PST)
Received: from ?192.168.168.101? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id 5sm1285760ywl.58.2009.02.18.16.37.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 18 Feb 2009 16:37:17 -0800 (PST)
Message-ID: <499CA9BB.8070506@gmail.com>
Date: Wed, 18 Feb 2009 16:37:15 -0800
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "mmox@ietf.org" <mmox@ietf.org>
References: <mailman.11.1234814402.16516.mmox@ietf.org> <27a487810902170721m31a157b1oed853cdd9cc6e500@mail.gmail.com> <548919.2383.qm@web82607.mail.mud.yahoo.com> <1234917818.6664.51.camel@localhost> <77186.32658.qm@web59104.mail.re1.yahoo.com> <499C7FAD.4080009@gmail.com> <2bd5b7f10902181404l40f2608fy6152ced5829a88ec@mail.gmail.com>
In-Reply-To: <2bd5b7f10902181404l40f2608fy6152ced5829a88ec@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [mmox] User Accounts / "Object" Transfer.
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, 19 Feb 2009 00:37:07 -0000

Suzy Deffeyes wrote:
> Can you elaborate on " physical spaces shared across interoperating 
> servers " and what you mean by that?


Let's assume organization A builds a space. Let's assume organization B 
builds furniture. Now, they want to have a meeting, and see how the 
furniture works in the space. The easiest way to accomplish this is to 
make organization A users log into the organization A virtual world 
(like they always do), and organization B users log into organization B 
virtual world (like they always do), and make arrangements such that 
some room/area/island within the two organizations is shared -- whatever 
comes to that space from A, also shows up in B, and vice versa. This 
allows A to publish its space, and B to bring the furniture to that 
space, without either having to disconnect from their regular virtual 
world (buddy list, unified messaging, inter-office collaboration, etc).

Sincerely,

jw