From swmp-bounces@ietf.org Fri Jul 06 16:13:39 2007
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 1I6uBP-0002lo-Mt; Fri, 06 Jul 2007 16:13:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6uBO-0002j7-Ss
	for swmp@ietf.org; Fri, 06 Jul 2007 16:13:38 -0400
Received: from e4.ny.us.ibm.com ([32.97.182.144])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6uBK-0002DM-Bl
	for swmp@ietf.org; Fri, 06 Jul 2007 16:13:38 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e4.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l66KDYfs020871
	for <swmp@ietf.org>; Fri, 6 Jul 2007 16:13:34 -0400
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l66KDXK7477110 for <swmp@ietf.org>; Fri, 6 Jul 2007 16:13:33 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1])
	by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l66KDXPZ008128 for <swmp@ietf.org>; Fri, 6 Jul 2007 16:13:33 -0400
Received: from internet1.lotus.com (internet1.lotus.com [9.33.9.11])
	by d01av04.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l66KDXIW008124
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 6 Jul 2007 16:13:33 -0400
Received: from wtfmail02.edc.lotus.com (wtfmail02.lotus.com [9.33.9.69])
	by internet1.lotus.com (8.14.1/8.14.1) with ESMTP id l66KDXi9004968;
	Fri, 6 Jul 2007 16:13:33 -0400 (EDT)
In-Reply-To: <46814E33.5020509@mediamachines.com>
To: "Jay C. Weber" <jweber@mediamachines.com>
Subject: [SWMP] Introducing pub-sub
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 August 18, 2005
Message-ID: <OFC969628A.0C4C557E-ON85257310.00690468-85257310.006F19D5@lotus.com>
From: john_patterson@us.ibm.com
Date: Fri, 6 Jul 2007 16:14:08 -0400
X-MIMETrack: Serialize by Router on WTFMAIL02/WTF/M/Lotus(Release
	7.0.2FP2|April 16, 2007) at 07/06/2007 04:14:09 PM,
	Serialize complete at 07/06/2007 04:14:09 PM
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
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="===============1294933816=="
Errors-To: swmp-bounces@ietf.org

This is a multipart message in MIME format.
--===============1294933816==
Content-Type: multipart/alternative;
	boundary="=_alternative 006F19D385257310_="

This is a multipart message in MIME format.
--=_alternative 006F19D385257310_=
Content-Type: text/plain; charset="US-ASCII"

Jay:

OK, I understand what you are doing with Hello.  I don't see a big problem 
with using it to activate the sending of latecomer information, but you 
are overloading its purpose a little.  It would be cleaner to use Hello 
for session establishment and a separate Subscribe message to activate 
latecomer sends.  Given the austere nature of swamp right now, this seems 
like overkill, but I do not think you can avoid it.

As you indicate, swamp has an implicit subscription to all the state that 
a network element has to support.  My guess is that we will not want that 
in the general case.  We will definitely want to ensure that one server 
can offer state sharing for multiple contexts (eg multiple pieces of the 
virtual world, sometimes called shards).  We will not want to do this via 
multiple ports, so the context of sharing will need to be brought into the 
protocol.  This will permit clients to indicate the shard that they need 
to learn about.

As a first approximation, we might say that a network element (client) can 
issue a Subscribe request and indicate which node is of interest.  This 
would establish a subscription to the state associated with that node and 
any under it in the tree.  Once we accept that the nodes need not be X3D 
nodes, but may be more general, then it is easy to imagine that each X3D 
model would be rooted in a Shard node, with each of those under a ROOT 
node.  A subscription to this shard node would indicate which piece of the 
world one wants to learn about and would cause the appropriate latecomer 
messages to be sent.

It is a small step to suggest that one network element might want more 
than one such subscription.  For example, I might want to know about the 
shard I am in and the shard I am about to enter.  This means I will want 
two subscriptions and, in general, I will want to be able to have an 
arbitrary number of subscriptions at one time.  Of course, if I can create 
subscriptions, then I will need to be able to get rid of them.  For this, 
I will want an Unsubscribe message (presumably indicating the node I am no 
longer interested in.)

With this approach, we might imagine the virtual world broken into square 
tiles or shards.  I would subscribe to the tile I am in and the eight that 
surround me.  As I move from tile to tile, I would drop and add 
subscriptions as needed.

If this makes sense, then you can see that Hello will need to let go of 
its subscription role and swmp will need to add Subscribe and Unsubscribe 
messages.

jfp

"Jay C. Weber" <jweber@mediamachines.com> wrote on 06/26/2007 01:34:43 PM:

> john_patterson@us.ibm.com wrote: 
> 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? 
>
> jweber@mediamachines.com replies
> 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
> 

--=_alternative 006F19D385257310_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Jay:</font>
<br>
<br><font size=2 face="sans-serif">OK, I understand what you are doing
with Hello. &nbsp;I don't see a big problem with using it to activate the
sending of latecomer information, but you are overloading its purpose a
little. &nbsp;It would be cleaner to use Hello for session establishment
and a separate Subscribe message to activate latecomer sends. &nbsp;Given
the austere nature of swamp right now, this seems like overkill, but I
do not think you can avoid it.</font>
<br>
<br><font size=2 face="sans-serif">As you indicate, swamp has an implicit
subscription to all the state that a network element has to support. &nbsp;My
guess is that we will not want that in the general case. &nbsp;We will
definitely want to ensure that one server can offer state sharing for multiple
contexts (eg multiple pieces of the virtual world, sometimes called shards).
&nbsp;We will not want to do this via multiple ports, so the context of
sharing will need to be brought into the protocol. &nbsp;This will permit
clients to indicate the shard that they need to learn about.</font>
<br>
<br><font size=2 face="sans-serif">As a first approximation, we might say
that a network element (client) can issue a Subscribe request and indicate
which node is of interest. &nbsp;This would establish a subscription to
the state associated with that node and any under it in the tree. &nbsp;Once
we accept that the nodes need not be X3D nodes, but may be more general,
then it is easy to imagine that each X3D model would be rooted in a Shard
node, with each of those under a ROOT node. &nbsp;A subscription to this
shard node would indicate which piece of the world one wants to learn about
and would cause the appropriate latecomer messages to be sent.</font>
<br>
<br><font size=2 face="sans-serif">It is a small step to suggest that one
network element might want more than one such subscription. &nbsp;For example,
I might want to know about the shard I am in and the shard I am about to
enter. &nbsp;This means I will want two subscriptions and, in general,
I will want to be able to have an arbitrary number of subscriptions at
one time. &nbsp;Of course, if I can create subscriptions, then I will need
to be able to get rid of them. &nbsp;For this, I will want an Unsubscribe
message (presumably indicating the node I am no longer interested in.)</font>
<br>
<br><font size=2 face="sans-serif">With this approach, we might imagine
the virtual world broken into square tiles or shards. &nbsp;I would subscribe
to the tile I am in and the eight that surround me. &nbsp;As I move from
tile to tile, I would drop and add subscriptions as needed.</font>
<br>
<br><font size=2 face="sans-serif">If this makes sense, then you can see
that Hello will need to let go of its subscription role and swmp will need
to add Subscribe and Unsubscribe messages.</font>
<br>
<br><font size=2 face="sans-serif">jfp</font>
<br>
<br><tt><font size=2>&quot;Jay C. Weber&quot; &lt;jweber@mediamachines.com&gt;
wrote on 06/26/2007 01:34:43 PM:<br>
<br>
&gt; john_patterson@us.ibm.com wrote: </font></tt>
<br><tt><font size=2>&gt; 4) &nbsp;It sounds like you are saying that latecomer
support is in your <br>
&gt; code even though it is not obvious how to do it based on the paper.
<br>
&gt; Does that mean there is a get request in your implemented protocol?
</font></tt>
<br><tt><font size=2>&gt;</font></tt>
<br><tt><font size=2>&gt; jweber@mediamachines.com replies</font></tt>
<br><tt><font size=2>&gt; In the client/server architecture we implemented,
when a client <br>
&gt; connects to the server and sends a Hello message, the server <br>
&gt; responds with a Hello message followed by a series of set messages
<br>
&gt; containing latecomer state data. &nbsp;So there is no explicit get
<br>
&gt; request, unless you want to consider Hello to subsume the semantics
<br>
&gt; &quot;send me latecomer data&quot;.<br>
&gt; <br>
&gt; Generalizing this issue a little, pub-sub requests are implicit in
<br>
&gt; our system. &nbsp;Our applications and supporting architectures don't
<br>
&gt; need explicit pub-subs, but I can imagine some uses for pub-sub <br>
&gt; messages, maybe we should add them to SWMP.<br>
&gt; <br>
&gt; jay<br>
&gt; <br>
</font></tt>
--=_alternative 006F19D385257310_=--


--===============1294933816==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1294933816==--




From swmp-bounces@ietf.org Fri Jul 06 16:24:57 2007
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 1I6uMK-0002Pr-VX; Fri, 06 Jul 2007 16:24:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6uMH-0002Pk-Eq
	for swmp@ietf.org; Fri, 06 Jul 2007 16:24:55 -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 1I6uMC-0004ci-S1
	for swmp@ietf.org; Fri, 06 Jul 2007 16:24:53 -0400
Received: from NEO (adsl-67-113-133-74.dsl.sntc01.pacbell.net [67.113.133.74])
	by william.mediamachines.com (Postfix) with ESMTP
	id AA2D2464442; Fri,  6 Jul 2007 15:23:33 -0500 (CDT)
From: "Tony Parisi" <tparisi@mediamachines.com>
To: <john_patterson@us.ibm.com>,
	"'Jay C. Weber'" <jweber@mediamachines.com>
Subject: RE: [SWMP] Introducing pub-sub
Date: Fri, 6 Jul 2007 13:24:37 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
In-Reply-To: <OFC969628A.0C4C557E-ON85257310.00690468-85257310.006F19D5@lotus.com>
thread-index: AcfACfkcw15oZmgYRbGIlNa2aZKmngAAaCcg
Message-Id: <20070706202333.AA2D2464442@william.mediamachines.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 442d80051e0361a34f3560325c4a7092
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="===============1135437161=="
Errors-To: swmp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1135437161==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0010_01C7BFD1.00B1A260"

This is a multi-part message in MIME format.

------=_NextPart_000_0010_01C7BFD1.00B1A260
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi John

 

Sounds reasonable to me.

 

For the uninitiated: can you elaborate on why we wouldn't want to do this
via multiple ports?

 

Thanks

Tony

 

 

  _____  

From: john_patterson@us.ibm.com [mailto:john_patterson@us.ibm.com] 
Sent: Friday, July 06, 2007 1:14 PM
To: Jay C. Weber
Cc: swmp@ietf.org
Subject: [SWMP] Introducing pub-sub

 


Jay: 

OK, I understand what you are doing with Hello.  I don't see a big problem
with using it to activate the sending of latecomer information, but you are
overloading its purpose a little.  It would be cleaner to use Hello for
session establishment and a separate Subscribe message to activate latecomer
sends.  Given the austere nature of swamp right now, this seems like
overkill, but I do not think you can avoid it. 

As you indicate, swamp has an implicit subscription to all the state that a
network element has to support.  My guess is that we will not want that in
the general case.  We will definitely want to ensure that one server can
offer state sharing for multiple contexts (eg multiple pieces of the virtual
world, sometimes called shards).  We will not want to do this via multiple
ports, so the context of sharing will need to be brought into the protocol.
This will permit clients to indicate the shard that they need to learn
about. 

As a first approximation, we might say that a network element (client) can
issue a Subscribe request and indicate which node is of interest.  This
would establish a subscription to the state associated with that node and
any under it in the tree.  Once we accept that the nodes need not be X3D
nodes, but may be more general, then it is easy to imagine that each X3D
model would be rooted in a Shard node, with each of those under a ROOT node.
A subscription to this shard node would indicate which piece of the world
one wants to learn about and would cause the appropriate latecomer messages
to be sent. 

It is a small step to suggest that one network element might want more than
one such subscription.  For example, I might want to know about the shard I
am in and the shard I am about to enter.  This means I will want two
subscriptions and, in general, I will want to be able to have an arbitrary
number of subscriptions at one time.  Of course, if I can create
subscriptions, then I will need to be able to get rid of them.  For this, I
will want an Unsubscribe message (presumably indicating the node I am no
longer interested in.) 

With this approach, we might imagine the virtual world broken into square
tiles or shards.  I would subscribe to the tile I am in and the eight that
surround me.  As I move from tile to tile, I would drop and add
subscriptions as needed. 

If this makes sense, then you can see that Hello will need to let go of its
subscription role and swmp will need to add Subscribe and Unsubscribe
messages. 

jfp 

"Jay C. Weber" <jweber@mediamachines.com> wrote on 06/26/2007 01:34:43 PM:

> john_patterson@us.ibm.com wrote: 
> 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? 
> 
> jweber@mediamachines.com replies 
> 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
> 


------=_NextPart_000_0010_01C7BFD1.00B1A260
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:sans-serif;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
tt
	{font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi =
John<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Sounds reasonable to =
me.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>For the uninitiated: can you =
elaborate on
why we wouldn&#8217;t want to do this via multiple =
ports?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Tony<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
john_patterson@us.ibm.com [mailto:john_patterson@us.ibm.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, July 06, =
2007 1:14
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Jay C. Weber<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> swmp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [SWMP] =
Introducing
pub-sub</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
</span></font><font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;
font-family:sans-serif'>Jay:</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>OK,
I understand what you are doing with Hello. &nbsp;I don't see a big =
problem
with using it to activate the sending of latecomer information, but you =
are
overloading its purpose a little. &nbsp;It would be cleaner to use Hello =
for
session establishment and a separate Subscribe message to activate =
latecomer
sends. &nbsp;Given the austere nature of swamp right now, this seems =
like
overkill, but I do not think you can avoid it.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>As
you indicate, swamp has an implicit subscription to all the state that a
network element has to support. &nbsp;My guess is that we will not want =
that in
the general case. &nbsp;We will definitely want to ensure that one =
server can
offer state sharing for multiple contexts (eg multiple pieces of the =
virtual
world, sometimes called shards). &nbsp;We will not want to do this via =
multiple
ports, so the context of sharing will need to be brought into the =
protocol. &nbsp;This
will permit clients to indicate the shard that they need to learn =
about.</span></font>
<br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>As
a first approximation, we might say that a network element (client) can =
issue a
Subscribe request and indicate which node is of interest. &nbsp;This =
would
establish a subscription to the state associated with that node and any =
under
it in the tree. &nbsp;Once we accept that the nodes need not be X3D =
nodes, but
may be more general, then it is easy to imagine that each X3D model =
would be
rooted in a Shard node, with each of those under a ROOT node. &nbsp;A
subscription to this shard node would indicate which piece of the world =
one
wants to learn about and would cause the appropriate latecomer messages =
to be
sent.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>It
is a small step to suggest that one network element might want more than =
one
such subscription. &nbsp;For example, I might want to know about the =
shard I am
in and the shard I am about to enter. &nbsp;This means I will want two =
subscriptions
and, in general, I will want to be able to have an arbitrary number of
subscriptions at one time. &nbsp;Of course, if I can create =
subscriptions, then
I will need to be able to get rid of them. &nbsp;For this, I will want =
an
Unsubscribe message (presumably indicating the node I am no longer =
interested
in.)</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>With
this approach, we might imagine the virtual world broken into square =
tiles or
shards. &nbsp;I would subscribe to the tile I am in and the eight that =
surround
me. &nbsp;As I move from tile to tile, I would drop and add =
subscriptions as
needed.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>If
this makes sense, then you can see that Hello will need to let go of its
subscription role and swmp will need to add Subscribe and Unsubscribe =
messages.</span></font>
<br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>jfp</span></font>
<br>
<br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&quot;Jay C.
Weber&quot; &lt;jweber@mediamachines.com&gt; wrote on 06/26/2007 =
01:34:43 PM:</span></font></tt><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<br>
<tt><font face=3D"Courier New">&gt; john_patterson@us.ibm.com wrote: =
</font></tt></span></font><br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt; 4)
&nbsp;It sounds like you are saying that latecomer support is in your =
</span></font></tt><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face=3D"Courier New">&gt; code even though it is not obvious =
how to do
it based on the paper. </font></tt><br>
<tt><font face=3D"Courier New">&gt; Does that mean there is a get =
request in your
implemented protocol? </font></tt></span></font><br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;</span></font></tt>
<br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;
jweber@mediamachines.com replies</span></font></tt> <br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt; In the
client/server architecture we implemented, when a client =
</span></font></tt><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face=3D"Courier New">&gt; connects to the server and sends a =
Hello
message, the server </font></tt><br>
<tt><font face=3D"Courier New">&gt; responds with a Hello message =
followed by a
series of set messages </font></tt><br>
<tt><font face=3D"Courier New">&gt; containing latecomer state data. =
&nbsp;So
there is no explicit get </font></tt><br>
<tt><font face=3D"Courier New">&gt; request, unless you want to consider =
Hello to
subsume the semantics </font></tt><br>
<tt><font face=3D"Courier New">&gt; &quot;send me latecomer =
data&quot;.</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; Generalizing this issue a little, =
pub-sub
requests are implicit in </font></tt><br>
<tt><font face=3D"Courier New">&gt; our system. &nbsp;Our applications =
and
supporting architectures don't </font></tt><br>
<tt><font face=3D"Courier New">&gt; need explicit pub-subs, but I can =
imagine
some uses for pub-sub </font></tt><br>
<tt><font face=3D"Courier New">&gt; messages, maybe we should add them =
to SWMP.</font></tt><br>
<tt><font face=3D"Courier New">&gt; </font></tt><br>
<tt><font face=3D"Courier New">&gt; jay</font></tt><br>
<tt><font face=3D"Courier New">&gt; =
</font></tt></span></font><o:p></o:p></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_0010_01C7BFD1.00B1A260--




--===============1135437161==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1135437161==--






From swmp-bounces@ietf.org Fri Jul 06 18:51:30 2007
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 1I6we7-0000Nw-V0; Fri, 06 Jul 2007 18:51:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6we4-0000G1-SY
	for swmp@ietf.org; Fri, 06 Jul 2007 18:51:24 -0400
Received: from e1.ny.us.ibm.com ([32.97.182.141])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6we4-0002A9-HA
	for swmp@ietf.org; Fri, 06 Jul 2007 18:51:24 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e1.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l66MoJmX021106
	for <swmp@ietf.org>; Fri, 6 Jul 2007 18:50:19 -0400
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l66MoJsh508060 for <swmp@ietf.org>; Fri, 6 Jul 2007 18:50:19 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1])
	by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l66MoJNw013054 for <swmp@ietf.org>; Fri, 6 Jul 2007 18:50:19 -0400
Received: from internet1.lotus.com (internet1.lotus.com [9.33.9.11])
	by d01av01.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l66MoJB6013036
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 6 Jul 2007 18:50:19 -0400
Received: from wtfmail02.edc.lotus.com (wtfmail02.lotus.com [9.33.9.69])
	by internet1.lotus.com (8.14.1/8.14.1) with ESMTP id l66MoIgP012071;
	Fri, 6 Jul 2007 18:50:19 -0400 (EDT)
In-Reply-To: <20070706202333.AA2D2464442@william.mediamachines.com>
To: "Tony Parisi" <tparisi@mediamachines.com>
Subject: RE: [SWMP] Introducing pub-sub
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 August 18, 2005
Message-ID: <OF6D7DADFE.BDE89499-ON85257310.007AA99F-85257310.007D7407@lotus.com>
From: john_patterson@us.ibm.com
Date: Fri, 6 Jul 2007 18:50:54 -0400
X-MIMETrack: Serialize by Router on WTFMAIL02/WTF/M/Lotus(Release
	7.0.2FP2|April 16, 2007) at 07/06/2007 06:50:55 PM,
	Serialize complete at 07/06/2007 06:50:55 PM
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0aa019322dfce838bd8604f5a841b57
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="===============0403639352=="
Errors-To: swmp-bounces@ietf.org

This is a multipart message in MIME format.
--===============0403639352==
Content-Type: multipart/alternative;
	boundary="=_alternative 007D740585257310_="

This is a multipart message in MIME format.
--=_alternative 007D740585257310_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Tony:

Well the truth is you caught me.  I was shooting from the hip when I said=20
that we should not use multiple ports.  I was writing about Subscribe and=20
it occurred to me that one could use multiple ports.  It seemed like a bad =

idea on the face of it, but I didn't really think it through any deeper=20
than that.

Having confessed the truth, let me see if I can ferret out some of the=20
reasons this seems like a bad idea.  My guess is that there are others=20
watching this list who understand networking better than I who will speak=20
with more authority.  Until they speak up, let's see what I can come up=20
with.

I guess the main reason is that I do not believe that ports come for free. =

 There is a large numbering space, but I assume the active ports actually=20
consume some amount of OS resources.  I am less familiar with UDP, but I=20
believe this is true for TCP.  If we wanted a server to support a hundred=20
shards using TCP, we would be listening on one hundred ports and then=20
shunting any client that connected over to a separate active port.  With n =

active clients we would be consuming 100 + n ports.  Or, in general, m + n =

ports, if m is the number of shards.

I am old enough to remember when we had a restricted number of ports, but=20
these days it is possible that m+n does not seem like such a burden. Let's =

look a little deeper and ask whether there are any other costs.

One other cost is the cost of publishing so many well known ports.  If we=20
register these in the name servers, then we are adding a lot of entries=20
for a rather specialized purpose.  If we do not register them, then we=20
will probably have to augment the protocol with a "name-service-like"=20
function that allows one well-known port to redirect activity to the other =

ports.  This seems a rather awkward arrangement for something that is=20
easily handled within the protocol.

Finally, there is the cost of creating and tearing down sessions as we=20
move from port to port.  This seems an unnecessary burden on our server=20
and our protocol.  It is even worse if we consider that authentication is=20
typically tied to the session and would now be occurring over and over as=20
we try to navigate from shard to shard.

I wasn't sure when I started this, but I think I convinced myself that my=20
first instincts were right.

Hope that helps.

jfp

> "Tony Parisi" <tparisi@mediamachines.com> wrote on 07/06/2007 04:24:37=20
PM:
>
> Hi John
>=20
> Sounds reasonable to me.
>=20
> For the uninitiated: can you elaborate on why we wouldn?t want to do
> this via multiple ports?
>=20
> Thanks
> Tony
>=20
>=20
>=20
> From: john=5Fpatterson@us.ibm.com [mailto:john=5Fpatterson@us.ibm.com]=20
> Sent: Friday, July 06, 2007 1:14 PM
> To: Jay C. Weber
> Cc: swmp@ietf.org
> Subject: [SWMP] Introducing pub-sub
>=20
>=20
> Jay:=20
>=20
> OK, I understand what you are doing with Hello.  I don't see a big=20
> problem with using it to activate the sending of latecomer=20
> information, but you are overloading its purpose a little.  It would
> be cleaner to use Hello for session establishment and a separate=20
> Subscribe message to activate latecomer sends.  Given the austere=20
> nature of swamp right now, this seems like overkill, but I do not=20
> think you can avoid it.=20
>=20
> As you indicate, swamp has an implicit subscription to all the state
> that a network element has to support.  My guess is that we will not
> want that in the general case.  We will definitely want to ensure=20
> that one server can offer state sharing for multiple contexts (eg=20
> multiple pieces of the virtual world, sometimes called shards).  We=20
> will not want to do this via multiple ports, so the context of=20
> sharing will need to be brought into the protocol.  This will permit
> clients to indicate the shard that they need to learn about.=20
>=20
> As a first approximation, we might say that a network element=20
> (client) can issue a Subscribe request and indicate which node is of
> interest.  This would establish a subscription to the state=20
> associated with that node and any under it in the tree.  Once we=20
> accept that the nodes need not be X3D nodes, but may be more=20
> general, then it is easy to imagine that each X3D model would be=20
> rooted in a Shard node, with each of those under a ROOT node.  A=20
> subscription to this shard node would indicate which piece of the=20
> world one wants to learn about and would cause the appropriate=20
> latecomer messages to be sent.=20
>=20
> It is a small step to suggest that one network element might want=20
> more than one such subscription.  For example, I might want to know=20
> about the shard I am in and the shard I am about to enter.  This=20
> means I will want two subscriptions and, in general, I will want to=20
> be able to have an arbitrary number of subscriptions at one time.=20
> Of course, if I can create subscriptions, then I will need to be=20
> able to get rid of them.  For this, I will want an Unsubscribe=20
> message (presumably indicating the node I am no longer interested in.)=20
>=20
> With this approach, we might imagine the virtual world broken into=20
> square tiles or shards.  I would subscribe to the tile I am in and=20
> the eight that surround me.  As I move from tile to tile, I would=20
> drop and add subscriptions as needed.=20
>=20
> If this makes sense, then you can see that Hello will need to let go
> of its subscription role and swmp will need to add Subscribe and=20
> Unsubscribe messages.=20
>=20
> jfp=20
>=20
--=_alternative 007D740585257310_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2 face=3D"sans-serif">Tony:</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Well the truth is you caught me. &nb=
sp;I
was shooting from the hip when I said that we should not use multiple ports.
&nbsp;I was writing about Subscribe and it occurred to me that one could
use multiple ports. &nbsp;It seemed like a bad idea on the face of it,
but I didn't really think it through any deeper than that.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Having confessed the truth, let me s=
ee
if I can ferret out some of the reasons this seems like a bad idea. &nbsp;My
guess is that there are others watching this list who understand networking
better than I who will speak with more authority. &nbsp;Until they speak
up, let's see what I can come up with.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">I guess the main reason is that I do
not believe that ports come for free. &nbsp;There is a large numbering
space, but I assume the active ports actually consume some amount of OS
resources. &nbsp;I am less familiar with UDP, but I believe this is true
for TCP. &nbsp;If we wanted a server to support a hundred shards using
TCP, we would be listening on one hundred ports and then shunting any client
that connected over to a separate active port. &nbsp;With n active clients
we would be consuming 100 + n ports. &nbsp;Or, in general, m + n ports,
if m is the number of shards.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">I am old enough to remember when we
had a restricted number of ports, but these days it is possible that m+n
does not seem like such a burden. &nbsp;Let's look a little deeper and
ask whether there are any other costs.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">One other cost is the cost of publis=
hing
so many well known ports. &nbsp;If we register these in the name servers,
then we are adding a lot of entries for a rather specialized purpose. &nbsp=
;If
we do not register them, then we will probably have to augment the protocol
with a &quot;name-service-like&quot; function that allows one well-known
port to redirect activity to the other ports. &nbsp;This seems a rather
awkward arrangement for something that is easily handled within the protoco=
l.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Finally, there is the cost of creati=
ng
and tearing down sessions as we move from port to port. &nbsp;This seems
an unnecessary burden on our server and our protocol. &nbsp;It is even
worse if we consider that authentication is typically tied to the session
and would now be occurring over and over as we try to navigate from shard
to shard.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">I wasn't sure when I started this, b=
ut
I think I convinced myself that my first instincts were right.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Hope that helps.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">jfp</font>
<br>
<br><tt><font size=3D2>&gt; &quot;Tony Parisi&quot; &lt;tparisi@mediamachin=
es.com&gt;
wrote on 07/06/2007 04:24:37 PM:<br>
&gt;<br>
&gt; Hi John</font></tt>
<br><tt><font size=3D2>&gt; &nbsp;</font></tt>
<br><tt><font size=3D2>&gt; Sounds reasonable to me.</font></tt>
<br><tt><font size=3D2>&gt; &nbsp;</font></tt>
<br><tt><font size=3D2>&gt; For the uninitiated: can you elaborate on why
we wouldn&#8217;t want to do<br>
&gt; this via multiple ports?</font></tt>
<br><tt><font size=3D2>&gt; &nbsp;</font></tt>
<br><tt><font size=3D2>&gt; Thanks</font></tt>
<br><tt><font size=3D2>&gt; Tony</font></tt>
<br><tt><font size=3D2>&gt; &nbsp;</font></tt>
<br><tt><font size=3D2>&gt; &nbsp;</font></tt>
<br><tt><font size=3D2>&gt; <br>
&gt; From: john=5Fpatterson@us.ibm.com [mailto:john=5Fpatterson@us.ibm.com]
<br>
&gt; Sent: Friday, July 06, 2007 1:14 PM<br>
&gt; To: Jay C. Weber<br>
&gt; Cc: swmp@ietf.org<br>
&gt; Subject: [SWMP] Introducing pub-sub</font></tt>
<br><tt><font size=3D2>&gt; &nbsp;</font></tt>
<br><tt><font size=3D2>&gt; <br>
&gt; Jay: <br>
&gt; <br>
&gt; OK, I understand what you are doing with Hello. &nbsp;I don't see
a big <br>
&gt; problem with using it to activate the sending of latecomer <br>
&gt; information, but you are overloading its purpose a little. &nbsp;It
would<br>
&gt; be cleaner to use Hello for session establishment and a separate <br>
&gt; Subscribe message to activate latecomer sends. &nbsp;Given the austere
<br>
&gt; nature of swamp right now, this seems like overkill, but I do not
<br>
&gt; think you can avoid it. <br>
&gt; <br>
&gt; As you indicate, swamp has an implicit subscription to all the state<b=
r>
&gt; that a network element has to support. &nbsp;My guess is that we will
not<br>
&gt; want that in the general case. &nbsp;We will definitely want to ensure
<br>
&gt; that one server can offer state sharing for multiple contexts (eg
<br>
&gt; multiple pieces of the virtual world, sometimes called shards). &nbsp;=
We
<br>
&gt; will not want to do this via multiple ports, so the context of <br>
&gt; sharing will need to be brought into the protocol. &nbsp;This will
permit<br>
&gt; clients to indicate the shard that they need to learn about. <br>
&gt; <br>
&gt; As a first approximation, we might say that a network element <br>
&gt; (client) can issue a Subscribe request and indicate which node is
of<br>
&gt; interest. &nbsp;This would establish a subscription to the state <br>
&gt; associated with that node and any under it in the tree. &nbsp;Once
we <br>
&gt; accept that the nodes need not be X3D nodes, but may be more <br>
&gt; general, then it is easy to imagine that each X3D model would be <br>
&gt; rooted in a Shard node, with each of those under a ROOT node. &nbsp;A
<br>
&gt; subscription to this shard node would indicate which piece of the
<br>
&gt; world one wants to learn about and would cause the appropriate <br>
&gt; latecomer messages to be sent. <br>
&gt; <br>
&gt; It is a small step to suggest that one network element might want
<br>
&gt; more than one such subscription. &nbsp;For example, I might want to
know <br>
&gt; about the shard I am in and the shard I am about to enter. &nbsp;This
<br>
&gt; means I will want two subscriptions and, in general, I will want to
<br>
&gt; be able to have an arbitrary number of subscriptions at one time.
&nbsp;<br>
&gt; Of course, if I can create subscriptions, then I will need to be <br>
&gt; able to get rid of them. &nbsp;For this, I will want an Unsubscribe
<br>
&gt; message (presumably indicating the node I am no longer interested
in.) <br>
&gt; <br>
&gt; With this approach, we might imagine the virtual world broken into
<br>
&gt; square tiles or shards. &nbsp;I would subscribe to the tile I am in
and <br>
&gt; the eight that surround me. &nbsp;As I move from tile to tile, I would
<br>
&gt; drop and add subscriptions as needed. <br>
&gt; <br>
&gt; If this makes sense, then you can see that Hello will need to let
go<br>
&gt; of its subscription role and swmp will need to add Subscribe and <br>
&gt; Unsubscribe messages. <br>
&gt; <br>
&gt; jfp <br>
&gt; </font></tt>
--=_alternative 007D740585257310_=--


--===============0403639352==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0403639352==--




From swmp-bounces@ietf.org Fri Jul 20 17:52:46 2007
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 1IC0P0-0005Dt-01; Fri, 20 Jul 2007 17:52:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IC0Oy-0005Do-KQ
	for swmp@ietf.org; Fri, 20 Jul 2007 17:52:44 -0400
Received: from mxi.ltu.se ([130.240.42.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IC0Ow-0000bR-Tp
	for swmp@ietf.org; Fri, 20 Jul 2007 17:52:44 -0400
Received: from EMMA.personal.adp.ltu.se (ross.personal.adp.ltu.se
	[130.240.150.6])
	by mxi.ltu.se (8.13.1/8.13.1) with ESMTP id l6KKqdWb005697;
	Fri, 20 Jul 2007 22:52:39 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 20 Jul 2007 23:52:40 +0200
Message-ID: <668D1B8AD729C94DB91D17EC19B8BB9104E84C43@EMMA.personal.adp.ltu.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SWMP server source
Thread-Index: AcfACiijrx0/oczdQ62qWTsmmy+wJQLDJIG6
References: <OFC969628A.0C4C557E-ON85257310.00690468-85257310.006F19D5@lotus.com>
From: "Sven-Erik Tiberg" <Sven-Erik.Tiberg@ltu.se>
To: "Jay C. Weber" <jweber@mediamachines.com>
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: swmp@ietf.org
Subject: [SWMP] SWMP server source
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="===============0209048637=="
Errors-To: swmp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0209048637==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CB18.4B0783F7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CB18.4B0783F7
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi.
=20
Plan to set up a SWMP -server on a newly installed fedora core 6 =
mashine.
and use the tips on =
http://community.mediamachines.com/comments.php?DiscussionID=3D336&page=3D=
1#Item_0
Any tips where to find the source.
=20
/BG
Sven-Erik Tiberg.

------_=_NextPart_001_01C7CB18.4B0783F7
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText92240 dir=3Dltr>=0A=
<DIV dir=3Dltr><TT><FONT face=3DArial size=3D2>Hi.</FONT></TT></DIV>=0A=
<DIV dir=3Dltr><TT><FONT face=3DArial size=3D2></FONT></TT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><TT><FONT face=3DArial size=3D2>Plan to set up a SWMP =
-server on a newly installed fedora core 6 mashine.</FONT></TT></DIV>=0A=
<DIV dir=3Dltr><TT><FONT face=3DArial size=3D2>and use the tips on <A =
href=3D"http://community.mediamachines.com/comments.php?DiscussionID=3D33=
6&amp;page=3D1#Item_0">http://community.mediamachines.com/comments.php?Di=
scussionID=3D336&amp;page=3D1#Item_0</A></FONT></TT></DIV>=0A=
<DIV dir=3Dltr><TT><FONT face=3DArial size=3D2>Any tips&nbsp;where to =
find the source.</FONT></TT></DIV>=0A=
<DIV dir=3Dltr><TT><FONT face=3DArial size=3D2></FONT></TT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><TT><FONT face=3DArial size=3D2>/BG</FONT></TT></DIV>=0A=
<DIV dir=3Dltr><TT><FONT face=3DArial size=3D2>Sven-Erik =
Tiberg.</FONT></TT></DIV></DIV></BODY></HTML>
------_=_NextPart_001_01C7CB18.4B0783F7--


--===============0209048637==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0209048637==--




