Re: [mmox] More LLIDL questions

Mark Lentczner <markl@lindenlab.com> Fri, 20 February 2009 17:07 UTC

Return-Path: <markl@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 8E05028C12B for <mmox@core3.amsl.com>; Fri, 20 Feb 2009 09:07:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.488
X-Spam-Level:
X-Spam-Status: No, score=-3.488 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 0hvwLdMWFITm for <mmox@core3.amsl.com>; Fri, 20 Feb 2009 09:07:24 -0800 (PST)
Received: from tammy.lindenlab.com (tammy.lindenlab.com [64.154.223.128]) by core3.amsl.com (Postfix) with ESMTP id BD59228C175 for <mmox@ietf.org>; Fri, 20 Feb 2009 09:07:24 -0800 (PST)
Received: from nil.lindenlab.com (nil.lindenlab.com [10.1.16.4]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tammy.lindenlab.com (Postfix) with ESMTP id EB2093DBC463 for <mmox@ietf.org>; Fri, 20 Feb 2009 09:07:38 -0800 (PST)
Message-Id: <58B39BFD-ECBB-4887-AC47-33D49E48B762@lindenlab.com>
From: Mark Lentczner <markl@lindenlab.com>
To: mmox@ietf.org
In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933D50262E1E@rrsmsx506.amr.corp.intel.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-4--855579137"
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 20 Feb 2009 09:07:38 -0800
References: <62BFE5680C037E4DA0B0A08946C0933D501FE18E@rrsmsx506.amr.corp.intel.com> <80E946E9-5C62-4E00-BE8C-A15513898F99@lindenlab.com> <62BFE5680C037E4DA0B0A08946C0933D50262DA8@rrsmsx506.amr.corp.intel.com> <50FD3E60-C7D4-4ACC-94BF-E05565A36D14@lindenlab.com> <62BFE5680C037E4DA0B0A08946C0933D50262E1E@rrsmsx506.amr.corp.intel.com>
X-Mailer: Apple Mail (2.930.3)
Subject: Re: [mmox] More LLIDL questions
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: Fri, 20 Feb 2009 17:07:25 -0000

On Feb 19, 2009, at 5:56 PM, Hurliman, John wrote:
> Last question. I found this snippet of LLIDL from the agent login  
> draft proposal on the Second Life wiki:
Gosh, I hope this won't be the *last* question! I'm really glad you  
are diving into this draft to this level of detail!

> agents: [ first_name: string, last_name: string ... ]

This was valid in an earlier, internal form of LLIDL. The intent was,  
as Meadhbh said, was to describe an array of values, grouped in twos.  
As you pointed out, the current valid way to do this is:

	agents: [ string, string, ... ]

The intent of the member-like names was so that the specification  
could name the members of the grouping, not that those members-like  
names appeared in the LLSD in any way. The confusion that ensued from  
that design seemed more than the utility it provided, so we removed it  
at a later stage. I think this discussion proves the point!

In any event, this kind of construction probably shouldn't be  
encouraged in APIs. Your alternative structure is far preferable from  
the standpoint of extensibility and understanding:

> agents: [ { first_name: string, last_name: string } ... ]

	- Mark


Mark Lentczner
Sr. Systems Architect
Technology Integration
Linden Lab

markl@lindenlab.com

Zero Linden
zero.linden@secondlife.com