[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Heartbeat
- Subject: Re: Heartbeat
- From: Patrick Lidstone
- Date: Mon, 07 Apr 2003 08:58:00 +0000
--- In <a
href="/group/xAP_developer/post?postID=T_zlWjf_LhsAiIHL1ekRXtnsYvXYwCGbf_63k9GuXAvmCc643oLVfckrVmtx29p0Y23CDnTSGh2tJvJWEsOkJBft2S0okAg">xAP_developer@xxxxxxx</a>,
Stuart Booth <lists@s...> wrote:
> On Fri, 04 Apr 2003 19:27:09 -0000, "Stuart Poulton"
> <stuart.poulton@a...> wrote:
>
> >Hi All,
> >
> >Does a heartbeat message have to contain the port that is being
used,
> >or is this only required for applications likely to encounter a
HUB ?
>
> Mine always do, as I don't know whether or not I'll encounter a hub
or
> not, or if the hub has died and is later restarted.
>
> I do have some events in my framework that inform the application
if a
> hub connection fails, and when a hub connection is made though.
>
If Stuart is thinking about the Rabbit, then it will never encounter
a hub, and technically there is no requirement to include the port
number I don't think this rule even breaks if a bridge is used to
join two xAP networks operating on different ports. But for
consistency and the sake of uniformity, I think all TCP/IP devices
should.
Patrick
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|