Re: [mmox] mmox Digest, Vol 1, Issue 113

"Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com> Tue, 24 February 2009 09:13 UTC

Return-Path: <infinity@lindenlab.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 165463A6A8A for <mmox@core3.amsl.com>; Tue, 24 Feb 2009 01:13:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.503
X-Spam-Level:
X-Spam-Status: No, score=-3.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, 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 qygCi7oS8ggF for <mmox@core3.amsl.com>; Tue, 24 Feb 2009 01:13:21 -0800 (PST)
Received: from tammy.lindenlab.com (tammy.lindenlab.com [64.154.223.128]) by core3.amsl.com (Postfix) with ESMTP id 56DD33A67FD for <mmox@ietf.org>; Tue, 24 Feb 2009 01:13:18 -0800 (PST)
Received: from [192.168.1.10] (dsl-63-249-112-43.cruzio.com [63.249.112.43]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tammy.lindenlab.com (Postfix) with ESMTP id 72BAF3DBC099; Tue, 24 Feb 2009 01:13:36 -0800 (PST)
Message-Id: <56A0F753-5C79-42D8-8063-913A0C70121C@lindenlab.com>
From: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
To: "dyerbrookme@juno.com" <dyerbrookme@juno.com>
In-Reply-To: <20090223.205743.9421.6@webmail20.vgs.untd.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 24 Feb 2009 01:13:34 -0800
References: <20090223.205743.9421.6@webmail20.vgs.untd.com>
X-Mailer: Apple Mail (2.930.3)
Cc: mmox@ietf.org, jwatte@gmail.com
Subject: Re: [mmox] mmox Digest, Vol 1, Issue 113
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: Tue, 24 Feb 2009 09:13:23 -0000

i think jon might have been asking what does "rez" mean in the context  
of this discussion.

it is the term we (second life and open sim) use to describe the  
process of placing a task into a region. unlike Entropia Universe and  
other prototype-based systems, second life and open sim "place" the  
item itself into a region. unlike nanocosm and other similar virtual  
worlds, copy restrictions are enforced not my instantiation limits but  
by moving an object from one's inventory to the simulator. the  
"rezzing" process is the bit of protocol that makes sure the simulator  
has properly instantiated the object in the simulator and potentially  
removes it from another (another sim or an inventory description.)

-cheers
-m

On Feb 23, 2009, at 5:57 PM, dyerbrookme@juno.com wrote:

> The information is the same as the object when the object itself was  
> all made up of information in the first place.
>
> The expression "rez" comes from the old science fiction novel Tron  
> from the 1980s, where there was a concept of a grid and things  
> appearing on it, so evidently it comes from the word "to resolve" as  
> in "to come into view" I believe -- but others might know better.
>
> I don't know why they didn't use the word "instantiate," perhaps  
> because it isn't an instance but a resolution.
>
> ____________________________________________________________
> Improve your driving ability with a stop at traffic school. Click now!
> http://thirdpartyoffers.juno.com/TGL2141/fc/BLSrjpTMLItIlvinHjvNdh8Lge0bJScMosX4pDGChGv9Xi7zuSFSaXqs4qU/
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox