Re: Strange Viewer issue

["Michael McSharry" <mcs101main@xxxxxxx>]

------=_NextPart_000_002B_01C44896.5E716300
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Seems to me that the port/uid topic is a result of trying to use the
header=
to identify items that are logical rather than physical entities.  (i.e. t=
he homeseer device).  Isn't the class schema better suited for abstract
rep=
resentations?
----- Original Message -----=20
From: James Traynor=20
To: xAP_developer@xxxxxxx=20
Sent: Wednesday, June 02, 2004 9:19 AM
Subject: Re: [xAP_developer] Strange Viewer issue



> Hmm - a little worried here - are you saying that xFx hubs are
differen=
t to
> the spec and handle this as a special case ?? Meaning that the
HomeSeer
> usage might break other hubs as they do not have this tweak ??=20
Patrick's works very well with it. I think the issue came because of the=
=20
internal separation and routing of messages that xFx does that a more=20
simple hub needs to do ;-)

Homeseer can be using up to 65 uids each with upto 99 sub ids. It, imho,=
=20
would be mad to have to create a port for each.
It would mean for every xAP message coming into homeseer for it to be=20
processed 65 times as each port would receive a copy of it. This would=20
then end up me only listening on one port, so as to remove the waste and=
=20
as transmitting doesn't use a hub the only thing using the ports would=20
be heartbeats.
so in reality all that would happen is my app would send out heartbeats=20
with fake port numbers and make the hub work really hard for no reason.

Port is just a way around the limitations of udp, if an app wants to use=
=20
separate ports then fine, I just see no reason at all to force this=20
issue. The only xAP hub that I haven't tried this with is the one in=20
xplhal but it should be easy enough to see if it works or not.
I can see the argument that it is good to know when a port is free=20
because the heartbeats have stopped, but I don't see how having multiple=
=20
heartbeats on one port causes any problems for this. what ever the=20
duration in a heartbeat is set to is the timeout value for the hub, if=20
there are 10 heartbeats each saying 60 seconds then this still works.=20
The only occasion for problems would be if the app sent multiple=20
heartbeats of different timeout times, agreed this would be a problem.=20
But this situation is unlikely to occur within a single app which in=20
reality the only time the multiple heartbeat/port issue would occur.

Think that makes sense, typing and thinking together don't always work :-=
0

James