The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Nuts and Bolts of a hub-app protocol


  • Subject: RE: Nuts and Bolts of a hub-app protocol
  • From: "Patrick Lidstone \(Personal e-mail\)" <patrick@xxxxxxxxxxxx>
  • Date: Sun, 10 Oct 2004 13:56:37 +0100


------=_NextPart_000_0001_01C4AED0.F65961E0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Michael,
Who's hub are you using, and which version? There are some subtle
differences between the flavours...
What you have described is basically correct: at startup, a connecting
app should send a heartbeat to the hub on port 3639, indicating which
port it is using for incoming messages. The port the application chooses
should be an unused (udp) port in the ephemeral port range (although
some early xap apps just allocated sequentially from 3639 onwards). Once
the heartbeat has been received, the hub should broadcast on
127.0.0.1:<allocated_port>. Early versions of some hubs incorrectly
used
the real ip address instead, although the principle was the same.
Rebroadcast on the allocated port by the hub will continue until at
least twice the hearbeat timeout interval, specified in the original
heartbeat message from the app to the hub, has expired.
HTH
Patrick

------=_NextPart_000_0001_01C4AED0.F65961E0
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1458" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>


<DIV><SPAN class=152183011-10102004><FONT face=Arial
color=#0000ff
size=2>Michael,</FONT></SPAN></DIV>
<DIV><SPAN class=152183011-10102004><FONT face=Arial
color=#0000ff size=2>Who's
hub are you using, and which version? There are some subtle differences
between
the flavours...</FONT></SPAN></DIV>
<DIV><SPAN class=152183011-10102004><FONT face=Arial
color=#0000ff size=2>What
you have described is basically correct: at startup, a connecting app
should
send a heartbeat to the hub on port 3639, indicating which port it is using
for
incoming messages. The port the application chooses should&nbsp;be an
unused
(udp) port in the ephemeral port range (although some early&nbsp;xap
apps just
allocated sequentially from 3639 onwards).&nbsp;Once the heartbeat has
been
received, the hub <EM>should</EM> broadcast on
127.0.0.1:&lt;allocated_port&gt;.
Early versions of some hubs incorrectly used the real ip address instead,
although the principle was the same. Rebroadcast on the allocated port by
the
hub will continue until at least twice the hearbeat timeout interval,
specified
in the original heartbeat message from the app to the hub,&nbsp;has
expired.</FONT></SPAN></DIV>
<DIV><SPAN class=152183011-10102004><FONT face=Arial
color=#0000ff
size=2>HTH</FONT></SPAN></DIV>
<DIV><SPAN class=152183011-10102004><FONT face=Arial
color=#0000ff
size=2>Patrick</FONT></SPAN></DIV><!-- **end egp
html banner** -->

<br>

<!-- **begin egp html banner** -->

<table border=0 cellspacing=0 cellpadding=2>
<tr bgcolor=#FFFFCC>
<td align=center><font size="-1"
color=#003399><b>Yahoo! Groups
Sponsor</b></font></td>
</tr>
<tr bgcolor=#FFFFFF>
<td align=center width=470><table border=0 cellpadding=0
cellspacing=0> <tr> <td align=center><font face=arial
size=-2>ADVERTISEMENT</font><br><a href="http://us.ard.yahoo.com/SIG=1294kikjp/M=295196.4901138.6071305.3001176/D=groups/S=1705007709:HM/EXP=1097499436/A=2128215/R=0/SIG=10se96mf6/*http://companion.yahoo.com";
alt=""><img src="http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_companion/lrec_companion_043004.gif";
alt="click here" width="300" height="250"
border="0"></a></td></tr></table>
</td>
</tr>
<tr><td><img alt="" width=1 height=1 src="http://us.adserver.yahoo.com/l?M=295196.4901138.6071305.3001176/D=groups/S=:HM/A=2128215/rand=183411542";></td></tr>
</table>

<!-- **end egp html banner** -->



<!-- **begin egp html banner** -->

<br>
<tt><hr width="500">
<b>Yahoo! Groups Links</b><br>
<ul>
<li>To visit your group on the web, go to:<br><a
href="http://groups.yahoo.com/group/xAP_developer/";>http://groups.yahoo.com/group/xAP_developer/</a><br>&nbsp;
<li>To unsubscribe from this group, send an email to:<br><a
href="mailto:xAP_developer-unsubscribe@xxxxxxx?subject=Unsubscribe";>xAP_developer-unsubscribe@xxxxxxx</a><br>&nbsp;
<li>Your use of Yahoo! Groups is subject to the <a href="http://docs.yahoo.com/info/terms/";>Yahoo!
Terms of Service</a>.
</ul>
</tt>
</br>

<!-- **end egp html banner** -->


</BODY></HTML>

------=_NextPart_000_0001_01C4AED0.F65961E0--




xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.