Re: [ogpx] LLSD/LLIDL implementations.

Dzonatas Sol <dzonatas@gmail.com> Wed, 24 March 2010 19:02 UTC

Return-Path: <dzonatas@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 D15953A68B3 for <ogpx@core3.amsl.com>; Wed, 24 Mar 2010 12:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 kkGP4AiZvwQG for <ogpx@core3.amsl.com>; Wed, 24 Mar 2010 12:02:44 -0700 (PDT)
Received: from mail-bw0-f211.google.com (mail-bw0-f211.google.com [209.85.218.211]) by core3.amsl.com (Postfix) with ESMTP id 34DFB3A6B90 for <ogpx@ietf.org>; Wed, 24 Mar 2010 12:02:29 -0700 (PDT)
Received: by bwz3 with SMTP id 3so6736503bwz.29 for <ogpx@ietf.org>; Wed, 24 Mar 2010 12:02:47 -0700 (PDT)
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=Qe66/R36EnztL7d+CvUaUpldYx9MKCwpv8XOn9HUMrk=; b=rLdiaBEwgJp8XXl1vHCcYm4/Q2DKK7yyzkoZPtdYj2bkTo3a79jL0XDYxtzaVnxvLs +pfCbxxZnuBXpe28WLrQl2GaxyUKBf81rctdHE3sD4Hn62I8CdoJuiIfA+roz987CV+j nqtsvE6HuI2TY3UtxJws3A1ALtIHYBl2EcNq4=
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=nlfsFoHIvFQ9ry806XP0w/lsQgzNS8hpZ2eenugsa+eoECZFnaThd/3sm0s5A+c3Gs ZQ8vAp6sA7QuQHlf1aqtJZiYrG5rIY6ajGS35IY+FiWt06dF5Qd50Dc7amQ6+Eac4p3s NA3vKCUimjOvliLoJO7634LStmKz5qM9oo450=
Received: by 10.204.10.151 with SMTP id p23mr5793943bkp.80.1269457364384; Wed, 24 Mar 2010 12:02:44 -0700 (PDT)
Received: from [192.168.0.50] (adsl-69-105-203-42.dsl.scrm01.pacbell.net [69.105.203.42]) by mx.google.com with ESMTPS id 13sm242117bwz.15.2010.03.24.12.02.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 24 Mar 2010 12:02:43 -0700 (PDT)
Message-ID: <4BAA6525.6050504@gmail.com>
Date: Wed, 24 Mar 2010 12:16:53 -0700
From: Dzonatas Sol <dzonatas@gmail.com>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707)
MIME-Version: 1.0
To: Mark Lentczner <markl@lindenlab.com>
References: <FA78869D-FF6F-477F-B810-C312F8ED00BF@lindenlab.com>
In-Reply-To: <FA78869D-FF6F-477F-B810-C312F8ED00BF@lindenlab.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ogpx <ogpx@ietf.org>
Subject: Re: [ogpx] LLSD/LLIDL implementations.
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <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: Wed, 24 Mar 2010 19:02:45 -0000

Mark Lentczner wrote:
> I put up a list of LLSD/LLIDL implementations that I knew about at the 
> session yesterday. Here it is again:
>
> C++: Linden Lab
> C#: OpenMetaverse
> Haskell: Linden Lab
> Java: Linden Lab, University of St. Andrews
> JavaScript: Linden Lab
> Perl: Linden Lab
> PHP: Linden Lab, SignpostMarv
> Python: Linden Lab
> Ruby: Linden Lab
>
> 1) If you have other LLSD implementations, please let me know. I'll 
> pull together a list of them.

There is a C# implementation of LLSD in MonoVida Communicator.
Used to implement a client-side REST/HTTP interface.

Project site: http://jira.dzonux.net:8080/browse/MVC
Contact: Ballard or "Dzonatas Sol"

Repository Browser: 
http://gitweb.dzonux.net/?p=communicator.git;a=tree;f=Source;hb=refs/heads/communicator

Resource documentation: 
https://wiki.secondlife.com/wiki/User:Dzonatas_Sol/SNOW-375_Resources
Implementation: https://jira.secondlife.com/browse/SNOW-375

More resources are added to take advantage of viewer's network protocol 
capabilities and features. To leverage VWRAP resources with these 
capabilities and features combined with SNOW-375 seems ideal. For 
example, specific implementations can be contained in separate programs 
and processes rather than all kept in a single threaded integrated 
design (as demonstrated by MonoVida). Vendors could provide there own 
signed-off implementation of a program used for connection negotiation 
to an agent domain (as their specific implementation of VWRAP that is 
distributed to the client). Such specific implementation, when signed, 
may be considered as an asset (where a 'generic' agent domain has the 
ability to store many 'specific implementations', as how inventory 
assets are now stored, and used on the client-side, as a 'script', to 
connect to other agent domains). Informally, this example is a concept 
of a VWRAP implementation via client-side scripting. Otherwise, the 
client-side REST/HTTP interface is intended to implement just 
client-side features at this time.