Re: [SWMP] Media Machines' initial design and code

"Jay C. Weber" <jweber@mediamachines.com> Tue, 26 June 2007 17:35 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 1I3Ex2-0003iR-Ti; Tue, 26 Jun 2007 13:35:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Ex1-0003iL-PD for swmp@ietf.org; Tue, 26 Jun 2007 13:35:39 -0400
Received: from worlds.webers.org ([64.34.168.199] helo=william.mediamachines.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3EwA-0005uB-DG for swmp@ietf.org; Tue, 26 Jun 2007 13:35:39 -0400
Received: from [192.168.2.119] (h-66-166-236-26.snvacaid.covad.net [66.166.236.26]) by william.mediamachines.com (Postfix) with ESMTP id 61B8146404E; Tue, 26 Jun 2007 12:33:42 -0500 (CDT)
Message-ID: <46814E33.5020509@mediamachines.com>
Date: Tue, 26 Jun 2007 10:34:43 -0700
From: "Jay C. Weber" <jweber@mediamachines.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: john_patterson@us.ibm.com
Subject: Re: [SWMP] Media Machines' initial design and code
References: <OF9311E6B3.E102E931-ON85257306.005BE41A-85257306.005DFDB9@lotus.com>
In-Reply-To: <OF9311E6B3.E102E931-ON85257306.005BE41A-85257306.005DFDB9@lotus.com>
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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>
Content-Type: multipart/mixed; boundary="===============0287298920=="
Errors-To: swmp-bounces@ietf.org

john_patterson@us.ibm.com wrote:
midOF9311E6B3.E102E931-ON85257306.005BE41A-85257306.005DFDB9@lotus.com" type="cite">4)  It sounds like you are saying that latecomer support is in your code even though it is not obvious how to do it based on the paper.  Does that mean there is a get request in your implemented protocol?
In the client/server architecture we implemented, when a client connects to the server and sends a Hello message, the server responds with a Hello message followed by a series of set messages containing latecomer state data.  So there is no explicit get request, unless you want to consider Hello to subsume the semantics "send me latecomer data".

Generalizing this issue a little, pub-sub requests are implicit in our system.  Our applications and supporting architectures don't need explicit pub-subs, but I can imagine some uses for pub-sub messages, maybe we should add them to SWMP.

jay


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