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

JeanRicard Broek <jeanricard.broek@gmail.com> Mon, 09 November 2009 13:48 UTC

Return-Path: <jeanricard.broek@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 55A4E28C0EB for <mmox@core3.amsl.com>; Mon, 9 Nov 2009 05:48:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.298
X-Spam-Level:
X-Spam-Status: No, score=-0.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_INCLDN=2.3]
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 HL8htHuLcIDq for <mmox@core3.amsl.com>; Mon, 9 Nov 2009 05:48:41 -0800 (PST)
Received: from mail-yx0-f192.google.com (mail-yx0-f192.google.com [209.85.210.192]) by core3.amsl.com (Postfix) with ESMTP id 72FCD3A69ED for <mmox@ietf.org>; Mon, 9 Nov 2009 05:48:41 -0800 (PST)
Received: by yxe30 with SMTP id 30so3241583yxe.29 for <mmox@ietf.org>; Mon, 09 Nov 2009 05:49:05 -0800 (PST)
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:content-type; bh=1MhQvFG6E/JEwpayDb5BLM0I2CWPRWRwgI7H2m+zzxE=; b=oH2WU3WB0G4sYice81Wz9VlMLX56SYHbjUUNv5nQ60cJ5TMsFvs0SwMUneLQj99nRR mjzOFkUEgUJLrKp8J1G70N7RjMUeC2QAnlxGFK0IuJI963wOmcDoVDkf6U2awp+daKUN naCMDm868q3KH9q/TwEdcVzHE06jTzVEQyt5U=
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 :content-type; b=SLfUK7pqd07pUPdJQP2LYJ3E9Qg9bVsbNAPuKw/gxJnFEc5qLcvlxQBJwkbtpUHXVe 8kXl+qA3MhyU5TnpnSEms5ntHDOnHJoiMf/PzLoqaSb7OZ9h4L9owNyj+2xgtRWseSuw 3mhekE2VYHIhV/FYqsnJyq+a3tDr2r+WSpOec=
MIME-Version: 1.0
Received: by 10.100.209.1 with SMTP id h1mr6122162ang.181.1257774208150; Mon, 09 Nov 2009 05:43:28 -0800 (PST)
In-Reply-To: <mailman.10.1257537602.25482.mmox@ietf.org>
References: <mailman.10.1257537602.25482.mmox@ietf.org>
Date: Mon, 9 Nov 2009 08:43:28 -0500
Message-ID: <d35db9370911090543o2592db55mefef2d9dfd822729@mail.gmail.com>
From: JeanRicard Broek <jeanricard.broek@gmail.com>
To: mmox@ietf.org
Content-Type: multipart/alternative; boundary=001636920216e26e420477f06009
Subject: Re: [mmox] mmox Digest, Vol 8, Issue 1
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: Mon, 09 Nov 2009 13:48:43 -0000

I would agree that VW interop is a puzzle & even more so it is puzzling.
Following Open Sim, Cablebeach, this list &
ogpx<https://www.ietf.org/mailman/listinfo/ogpx>;,
Sirakata, and realXtend, one is left like Plato seeing only moving shadows.

Is there anyplace or has anyone captured a comprehensive view of the state
of the art in some reasonable wiki like format. If nothing else a simple map
to the players and technologies showing the interrelationship of components
and just what things are being developed or integrated into each project?.

The first step I will take is to contact people one an one to just create a
listing of each piece of the puzzle or architectural component  and then see
what is being done in each area, asking who ,what, were, when, and why for
each. Maybe then we can all get some idea what the picture looks like.
Suggested subjects so far are:

Identity & Authentication
Asset identification, storage & transfer
Rendering Engines (Ogre, LL/Windlight, irrlicht )
Server Side Rendering/Streaming (Onlive, Nvidia Reality Server)
Mesh support, Mesh Avatars, Animation, Collada, converters
Prim size limits and megaregions.
Databases (MySQL, SQLServer, SQLite,Others)
Advanced Search of region assets & Identities
HTTP & Media on a prim, etc
Audio & VoIP
Scripting (Python, LUA, LSL)
GUI/Viewer controls, frameworks Qt, etc
Browser Plugins
APIs

Contact jeanricard.broek@gmail.com if you have suggestions, anything to
contribute to the above, and/or would like a link to whatever I manage to
compile.

tks JR

On Fri, Nov 6, 2009 at 3:00 PM, <mmox-request@ietf.org>; wrote:

> If you have received this digest without all the individual message
> attachments you will need to update your digest options in your list
> subscription.  To do so, go to
>
> https://www.ietf.org/mailman/listinfo/mmox
>
> Click the 'Unsubscribe or edit options' button, log in, and set "Get
> MIME or Plain Text Digests?" to MIME.  You can set this option
> globally for all the list digests you receive at this point.
>
>
>
> Send mmox mailing list submissions to
>        mmox@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://www.ietf.org/mailman/listinfo/mmox
> or, via email, send a message with subject or body 'help' to
>        mmox-request@ietf.org
>
> You can reach the person managing the list at
>        mmox-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mmox digest..."
>
> Today's Topics:
>
>   1. Re: Rough draft of the Cable Beach Core protocol is online
>      (Morgaine)
>   2. (no subject)
>
>
> ---------- Forwarded message ----------
> From: Morgaine <morgaine.dinova@googlemail.com>;
> To: MMOX-IETF <mmox@ietf.org>;
> Date: Fri, 6 Nov 2009 07:51:31 +0000
> Subject: Re: [mmox] Rough draft of the Cable Beach Core protocol is online
> What's the latest on Cable Beach, John?
>
> We occasionally hear snippets of information about "working with John on
> changes to Cable Beach" from various quarters, including LL (we are told),
> realXtend, and Opensim, but it's hard to gain an overall perspective on
> where CB is heading, whether there are conflicting interests pulling on its
> design, if they're being resolved, and how it's all coming together.
>
> Seeing as CB appears to be central to (or at least involved in) the future
> of several projects, one of which is VWRAP, I expect that there is a lot of
> interest in the evolution of its design.  The news page at
> http://code.google.com/p/cablebeach/ shows that CB is indeed making good
> progress (a new download yesterday!), but the CB mailing list is moribund
> because all the interesting discussion occurs over IRC, which is hard to
> reference retrospectively.  Are there archives?  It's difficult to get a
> handle on what's happening currently unless one is permanently connected to
> the IRC channel.
>
> Be that as it may, I think that occasional outlines of the latest in design
> thinking would help many people understand how CB is evolving as part of the
> VW interop puzzle --- the realXtend mailing list is a poster child in that
> respect, they're doing a great job.  Updates on the CB mailing list would
> revive it nicely too, as it contains more spam than on-topic posts
> currently. :-(
>
> Keep up the good work! :-)
>
> Morgaine.
>
>
>
> ===================================
>
> On Thu, Jul 2, 2009 at 3:01 AM, Hurliman, John <john.hurliman@intel.com>wrote:
>
>> http://code.google.com/p/cablebeach/wiki/CableBeachCore1_0
>>
>>
>
> ---------- Forwarded message ----------
> From:
> To:
> Date:
> Subject:
> <br>
> Introduction<br>
> <br>
> Virtual worlds are made up of a complex stack of services that operate
> toge=
> ther to deliver a complete immersive experience. The approach that virtual
> =
> worlds have taken so far is to build an entire vertical stack of services
> i=
> ncluding user account management, content distribution servers, inventory
> h=
> osting, simulation servers, simulation coordinators, and more. As virtual
> w=
> orlds grow in both popularity and complexity, it is no longer always
> desira=
> ble to only build so-called &quot;walled gardens&quot; of services. Cable
> B=
> each provides the glue to bind virtual world services together, whether
> the=
> y exist alongside one another in a data center or across the Internet run
> b=
> y different administrators that have no preexisting relationship. The
> prima=
> ry focus of the architecture is on the following:<br>
>
> <br>
>  =A0 =A0* Let service providers specialize in what they do best. To
> address=
>  the growing scalability demands of the web, service providers have
> evolved=
>  into providing narrow but high quality services. You wouldn&#39;t expect
> a=
>  social network to also provide the best search engine service on the
> web.<=
> br>
>
>  =A0 =A0* Use existing standards. Many of the challenges in virtual worlds
> =
> are broad issues that are also being addressed by the web community.
> Instea=
> d of creating new parallel solutions, Cable Beach attempts to leverage as
> m=
> uch existing technology as it can to enable better compatibility with
> other=
>  architectures, both today and in the future.<br>
>
>  =A0 =A0* Give virtual world administrators more flexibility, not less. No
> =
> use case is viewed as more or less valid than another, and the system does
> =
> not favor any particular setup. Building a walled garden is just as easy
> as=
>  building a completely decentralized world, or any combination of the
> two.<=
> br>
>
> <br>
> The core of Cable Beach is the definition of a world service, a virtual
> wor=
> ld login protocol, and a standard method of defining virtual world
> services=
> . The implementation available at this site consists of a server for a
> worl=
> d service and another server for assets and filesystem services.
> Initially,=
>  this implementation is targeting compatibility with the OpenSim project
> us=
> ing a custom OpenSim extension called ModCableBeach. Additional connectors
> =
> for other virtual world systems are in the planning phase.<br>
>
> <br>
> ---<br>
> John<br>
> _______________________________________________<br>
> mmox mailing list<br>
> <a href=3D"mailto:mmox@ietf.org">mmox@ietf.org</a><br>
> <a href=3D"https://www.ietf.org/mailman/listinfo/mmox"
> target=3D"_blank">ht=
> tps://www.ietf.org/mailman/listinfo/mmox</a><br>
> </blockquote></div><br>
>
> --0016e6d5667ab4205c0477af1cf5--
>
>
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>
>