Re: Port Mapping Questions

[Mark Harrison \(Yahoo!\)]

John,

Yes - in retrospect, that's what we should have done.

The trouble is, the "additional port binding" bit is in the spec,
and was
already out, and widely in use before I picked up on it. We have discussed
this in the past, and decided to pretty much leave it "as is" in
the
interests of stability.

Worth noting that xAPplications _do_ check for other applications bound to
a
port first, so the problem only occurs if the other application starts
AFTER
a xAPplication binds... and it won't be the first to start either :-(

I'm aware of at least one home installation with over a hundred xAP
applications running... but nothing like the 226 that would be required to
hit xPL.... and they certainly AREN'T all on the same PC :-) (most are
hardware telemetry devices.)

M.

----- Original Message -----
From: "John B" <<a
href="/group/xAP_developer/post?postID=1QXtd7r9G1I0qtoHUA4dnBuzheOHEh3xv-DYjYfd8NUjzN-TTSdfxs5CZMcRZJqVojjWDwHMFd52seGW_cku2drR_vJHGc5-ZnaK">home-automation@j...</a>>
To: <<a
href="/group/xAP_developer/post?postID=Z8Gqqgdq4KU_cPU3X0ZkcI8_Bsco3lVFKbk5AeadUaYW75uNTVMoxchK72T2awFLv9KeUcO8B_-6SYYAYl-3cyooIw">xAP_developer@xxxxxxx</a>>
Sent: Thursday, March 18, 2004 6:51 AM
Subject: Re: [xAP_developer] Port Mapping Questions


> Hi Stuart,
>
> > xAPListeningIP" is the IP address that the application
connects to on
> > the local machine. It finds a the first free port from 3639 and
binds
> > to that address for incoming data. It is this port number that it
> > pumps out in the Port= parameter of its heartbeats, as you'd
expect.
>
> This is technically not how a TCP/IP application should operate.
> Remember that xAP has only been allocated port 3639, so using ports
3640,
3641 etc. means you are using ports that have been reserved for use by
other
protocols.
> (indeed, if you went up high enough you'd reach 3865, which is the xPL
port :-))
>