Re: [ogpx] Tourist use case

Vaughn Deluca <vaughn.deluca@gmail.com> Fri, 16 October 2009 22:46 UTC

Return-Path: <vaughn.deluca@gmail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8324C3A68CD for <ogpx@core3.amsl.com>; Fri, 16 Oct 2009 15:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level:
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[AWL=-0.355, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_OEM_OBFU=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 kf0EwgUy3SBD for <ogpx@core3.amsl.com>; Fri, 16 Oct 2009 15:46:51 -0700 (PDT)
Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by core3.amsl.com (Postfix) with ESMTP id 3D6373A6949 for <ogpx@ietf.org>; Fri, 16 Oct 2009 15:46:51 -0700 (PDT)
Received: by fxm18 with SMTP id 18so2995393fxm.37 for <ogpx@ietf.org>; Fri, 16 Oct 2009 15:46:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=6eY4uO2bLqs2BLDYstl8TkDTceGwvseWzqDVxa9X00o=; b=ayW6WT+GY2AZCQCc2ECdJ7t/NvQLZoOsvqVyw0NPmy0wvhCcn0ZFk//LP8LpJVw/kU Qsv0yCZswAyfrj8LFpeuw19T3DKIVLJNBtN5ad/FmB8PmYZj/Ydsl4nvaOEVzf+ENo71 g/q2HC46MxAlt6xL8EB6mGn0fJ8EirnFG1cC8=
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=nezp63c8E85qmv6gPQrF08GFOhuXOrBlVk2V6hTpz4AB5GNvkCP6db8wc5MnFP5+nr oWQoexFd5KHXU+oRWKC3FBO3j28gxijceKauMB5wSoU1IzRUN1m4OHodFoZZGfEKlyW+ Vvzkp2pWRTpWr9X+uGICaJ0nFXQP9GmQxt1sg=
MIME-Version: 1.0
Received: by 10.204.175.80 with SMTP id w16mr1796666bkz.207.1255733212292; Fri, 16 Oct 2009 15:46:52 -0700 (PDT)
In-Reply-To: <f72742de0910161003k5cdee053hf1088be0b3636edb@mail.gmail.com>
References: <9b8a8de40910160034j11dcb94fm401f29814aed60a8@mail.gmail.com> <3a880e2c0910160116g7a7e488fpe03b10d9b534aa35@mail.gmail.com> <e0b04bba0910160151k1c5a1fcejab7a7f6c386fefb3@mail.gmail.com> <b8ef0a220910160639v48f1d447ob175a0c5d53dc263@mail.gmail.com> <4AD894BE.30501@uci.edu> <f72742de0910161003k5cdee053hf1088be0b3636edb@mail.gmail.com>
Date: Sat, 17 Oct 2009 00:46:52 +0200
Message-ID: <9b8a8de40910161546h9e54dcah59cb423a0ac096af@mail.gmail.com>
From: Vaughn Deluca <vaughn.deluca@gmail.com>
To: Joshua Bell <josh@lindenlab.com>
Content-Type: multipart/alternative; boundary=00032555b93a0d2a5f0476152c95
Cc: ogpx@ietf.org
Subject: Re: [ogpx] Tourist use case
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2009 22:46:52 -0000

On Fri, Oct 16, 2009 at 7:03 PM, Joshua Bell <josh@lindenlab.com> wrote:

> On Fri, Oct 16, 2009 at 8:43 AM, Sean Hennessee <sean@uci.edu> wrote:
>
>> Meadhbh Hamrick wrote:
>>
>>> On Fri, Oct 16, 2009 at 1:51 AM, Morgaine
>>> <morgaine.dinova@googlemail.com> wrote:
>>>
>>>> On Fri, Oct 16, 2009 at 9:16 AM, Infinity Linden (Meadhbh Hamrick)
>>>> <infinity@lindenlab.com> wrote:
>>>>
>>>>  also. just a show of hands. who's planning on implementing the tourist
>>>>> model?
>>>>
>>>>  [...]


> There are two distinct definitions in extremely common use on the 'net:
>
> (1) to implement: write the code for something
> (2) to implement: configure and deploy code for something
>
> My interpretation of this thread is that Infinity is using definition #1,
> Sean and Morgaine are using definition #2. Infinity is asking specifically:
> "who will write the code that adds support for the protocol to a piece of
> software?" not "who will make use of software that implements the protocol?"
>

*ahum* I was most definitely using  definition #2. Yet, i *can* code, and
given the importance of this aspect, i am certainly willing to assist in
making this use case happen. However, i am not a professional programer, but
just a scientist, coding my own analysis softeware. So i am likely to need a
bit of help from some friends :)

On the other hand, i am convinced that a proper implementation of the SL use
case (this time in the sense of definition  #1) will generate about  all the
code we need for the tourist case. The difference between the SL model and
the tourist model is largely at the policy level.  But when we get down to
the specs, that will become clear soon enough.

Regarding the coding, i think Agent Domain code was written this summer. Is
that available somewhere? i would like to have a look at that, to get a
better feel for the size of the problem.

-Vaughn


> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>