Re: Communicatiing with xplHal

[Mal Lansell <mlansell@xxxxxxxxxxxxxx>]

Tony Tofts wrote:

>Hi Mal,
>
>Just to make things clear,
>
>You don't connect to xplhal, you connect to a hub using a port 50000+
>
>
>
Doh! (slaps forehead).  Forgot that bit ;-)

>(basically you try to open a connection to listen for udp packets
probably
>on localhost on 50000, if it's in use (fails) then try port 50001 etc
etc
>
>The hub listens on port 3865 (broadcast) and relays the messages to all
>attached app's (that are listening on 50000+ preferably). If you use
the vb6
>hub for testing, you'll see if your app is attaching ok as it will be
>listed, I think the vb.net version, windows service, logs to the system
or
>app log)
>
>The application sends a broadcast to port 3865 (i.e. outgoing doesn't
go
>thru hub)
>
>
>
Ok, so this is what I'm doing at the moment.  I create a socket, connect
to port 3865, send my config.app heartbeat, and then close the socket.
This appears to work, but is it the right way to do it?

I also create another socket, and set it to listen for incoming
connections, but nothing happens.  I let Windows choose the port number,
and send whatever it comes up with in my config.app message - it may be
that it is less than 50000 - does this actually matter?

>Just post to the list your required vendor id and as long as it's valid
and
>not already take it will be yours :-)
>
>
>
Following the existing convention, I suppose it should be MALL, but that
makes me look like a shopping centre, so perhaps just MAL would be
better, if that's enough letters!

Mal