Re: [SWMP] Kicking things off

Braden McDaniel <braden@endoframe.com> Tue, 29 May 2007 17:55 UTC

Return-path: <swmp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ht5v6-0003Lb-Sd; Tue, 29 May 2007 13:55:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ht5v5-0003LS-Cx for swmp@ietf.org; Tue, 29 May 2007 13:55:43 -0400
Received: from lax-green-bigip-5.dreamhost.com ([208.113.200.5] helo=friskymail-a1.g.dreamhost.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ht5v4-00029C-37 for swmp@ietf.org; Tue, 29 May 2007 13:55:43 -0400
Received: from [192.168.1.21] (ip70-179-64-52.dc.dc.cox.net [70.179.64.52]) by friskymail-a1.g.dreamhost.com (Postfix) with ESMTP id 530715F570; Tue, 29 May 2007 10:55:41 -0700 (PDT)
Subject: Re: [SWMP] Kicking things off
From: Braden McDaniel <braden@endoframe.com>
To: giles@yumetech.com
In-Reply-To: <465C60D7.3020202@yumetech.com>
References: <46604A7B.30308@mediamachines.com> <465C5993.5040805@yumetech.com> <1180458854.3584.16.camel@hinge.endoframe.net> <465C60D7.3020202@yumetech.com>
Content-Type: text/plain
Date: Tue, 29 May 2007 13:55:40 -0400
Message-Id: <1180461340.3584.33.camel@hinge.endoframe.net>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6)
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: swmp@ietf.org
X-BeenThere: swmp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of a Simple Wide-area Multiuser-3D Protocol <swmp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/swmp>, <mailto:swmp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/swmp>
List-Post: <mailto:swmp@ietf.org>
List-Help: <mailto:swmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/swmp>, <mailto:swmp-request@ietf.org?subject=subscribe>
Errors-To: swmp-bounces@ietf.org

On Tue, 2007-05-29 at 10:20 -0700, Alan Hudson wrote:

[snip]

> I found a power point slide here:
> 
> http://www.google.com/url?sa=t&ct=res&cd=1&url=http%3A%2F%2Fwww.dtic.mil%2Fndia%2F2006test%2Fhudgins.pdf&ei=tV9cRuCMPJXmgQPQ2ISRBQ&usg=AFrqEzfxshHV-vgke_DVfAbBeaMw6xzg0Q&sig2=Zv-fDXeO5Lo0s8OxcOn45Q
> 
> Slide 34(TENA Solutions to Interoperability Challenges) talks about 
> On-the-wire specification and says this:
> 
> API Standard allows future technological advances for data transmission
> to be much more cost-effectively incorporated
> 
> I had taken this to mean that TENA took the same approach as HLA.

Heh... I don't know that that prose *means* anything. ;-)

Keep in mind that TENA is a software product whereas HLA is a spec. TENA
makes no pretense to vendor-independence.

As I mentioned, TENA is built on top of CORBA. The DMSO RTI (an HLA
implementation) was built on CORBA, too. But it was implementing a
abstraction independent of CORBA (or much else); as such, the fact that
it was using CORBA under the hood was not terribly relevant.

Since TENA is a particular implementation that implements an abstraction
*in terms of* CORBA, you can go to the (generated) CORBA IDL files for
ground truth. Though in practice, I cannot imagine someone wanting to
*talk* to TENA apps via the TENA mechanisms without themselves *being* a
TENA app.

[I don't think this is particularly topical to the SWMP list. If you'd
like to know more about TENA, we should probably continue this
off-list.]

-- 
Braden McDaniel                           e-mail: <braden@endoframe.com>
<http://endoframe.com>                    Jabber: <braden@jabber.org>



_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp