<html><body><html o="urn:schemas-microsoft-com:office:office" w="urn:schemas-microsoft-com:office:word" m="http://schemas.microsoft.com/office/2004/12/omml"><head><meta name="viewport" content="width=device-width" /><meta http-equiv="Content-Type" content="text/vnd.ui.insecure+html;charset=utf-8" /></head><body lang="EN-US" style="overflow-wrap:break-word; word-break: break-word;"><div class="mail_android_message" style="line-height: 1; padding: 0.5em">John,<br>
<br>
When you say "pub/sub vs. messaging" do I get you right you mean "using a central server yes vs. no" ?<br>
<br>
Messages are addressed to concrete destinations vs. publishing a state always to a server?<br>
<br>
This the topic you want to discuss?<br>
<br>
Thanks<br>
-- <br>
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.</div><div class="mail_android_quote" style="line-height: 1; padding: 0.3em">Am 01.04.19, 00:51, Christoph Valentin <christoph.valentin@gmx.at> schrieb:<blockquote class="gmail_quote" style="margin: 0.8ex 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)" /><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:472253142;
mso-list-type:hybrid;
mso-list-template-ids:286569224 -1 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><meta name="viewport" content="width=device-width" /><div class="mail_android_message" style="line-height: 1; padding: 0.5em">Hi John,<br />
<br />
About pub/sub. I am not aware of this abbreviation, but let me guess you mean "publish" / "subscribe" and let me assume we are talking about network functions well known as so called brokers. <br />
<br />
<br />
<br />
The Network Sensor node is exactly such an interface that is used to communicate with a broker (aka collaboration server).<br />
<br />
<br />
<br />
When the NS is initialized, then it sends an STS "Subscribe to Stream" to the broker and tells him about the interest <br />
<br />
<br />
When a new state is published, then this is done with a SUN "State Update Notification".<br />
<br />
Publishing is done by SURE "State Update Request" and SCR "State Change Request<br />
<br />
All the best <br />
-- <br />
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.</div><div class="mail_android_quote" style="line-height: 1; padding: 0.3em">Am 01.04.19, 00:35, John Carlson <yottzumm@gmail.com> schrieb:<blockquote class="gmail_quote" style="margin: 0.8ex 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="WordSection1"><p class="MsoNormal"></p><p> </p><p class="MsoNormal">What do you think about using pub/sub or messaging? What “style” of protocol works best in SP-ARK’s case? I think one to many and many to one is one of the best features of pub/sub, but often it takes a lot infrastructure to maintain the queues.</p><p></p><p class="MsoNormal"></p><p> </p><p class="MsoNormal">Maybe we should step back and define the objects we are communicating.</p><p></p><p class="MsoNormal"></p><p> </p><ol style="margin-top:0in" start="1" type="1"><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Avatar (initial H-Anim figure) and position, orientation, motion (ongoing). This is done by pc.multiplayer tag around the world<p></p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Things the avatar might be carrying (shapes transformed by the avatars position, orientation and motion)<p></p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Sounds-chat-video applied to avatar position<p></p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">???<p></p></li></ol><p class="MsoNormal"></p><p> </p><p class="MsoNormal"></p><p> </p><p class="MsoNormal"></p><p> </p><p class="MsoNormal">Thus some actions might be:</p><p></p><p class="MsoNormal"></p><p> </p><p class="MsoNormal">Subscribe to Avatar Topic, Reply Address</p><p></p><p class="MsoNormal">Subscribe to Inventory Topic, Reply Address</p><p></p><p class="MsoNormal">Subscribe to Communication Topic, Reply Address</p><p></p><p class="MsoNormal">Avatar Publish</p><p></p><p class="MsoNormal">Inventory Publish</p><p></p><p class="MsoNormal">Communication Publish</p><p></p><p class="MsoNormal">Receive Avatar Publish</p><p></p><p class="MsoNormal">Receive Inventory Publish</p><p></p><p class="MsoNormal">Receive Communication Publish</p><p></p><p class="MsoNormal"></p><p> </p><p class="MsoNormal">This feels a lot more natural to me than the SQL, Chat or REST protocols.</p><p></p><p class="MsoNormal"></p><p> </p><p class="MsoNormal">We can create different topics to communicate about, probably subclasses of NetworkSensor or some such.</p><p></p><p class="MsoNormal"></p><p> </p><p class="MsoNormal">Check out the High Fidelity intro video for ideas about what might be done, re: Inventory. This will be important when we get to VR controllers.</p><p></p><p class="MsoNormal"></p><p> </p><p class="MsoNormal">Collaboration as far as the scene itself is a lot like SAI, but perhaps we need to consider network traffic for that?</p><p></p><p class="MsoNormal"></p><p> </p><p class="MsoNormal">Don, what do you think about putting a network pub/sub interface into the event loop for X3Dv4? Is there a popular JavaScript pub/sub?<i></i></p><p><i></i></p><p class="MsoNormal"></p><p class="MsoNormal"></p><p> </p><p class="MsoNormal">John</p><p></p></div></blockquote></div>_______________________________________________
x3d-public mailing list
x3d-public@web3d.org
http://web3d.org/mailman/listinfo/x3d-public_web3d.org
</blockquote></div></body></html></body></html>