[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: xPLLib v3.0 Public Beta
----- Original Message -----
From: "Tom Van den Panhuyzen" <tomvdp@xxxxxxx>
To: <ukha_xpl@xxxxxxx>
Sent: Wednesday, December 01, 2004 6:20 PM
Subject: Re: [ukha_xpl] xPLLib v3.0 Public Beta
>
> On Wed, 1 Dec 2004 09:52:00 -0000, Mal Lansell
<mlansell@xxxxxxx>
wrote:
> > A few questions:
> >
> > 1) Tom said earlier "If a user has xpl windows applications
and no xpl
> > services then it is of course better to have a dedicated
hub". Why? If
the
> > hub can transfer, then any running app can provide the hub
functions.
>
> If you know beforehand the user will be switching xpl apps on and off
> and each will in fact start/stop a hub, then it is perhaps better to
> just provide the hub as a seperate service that is always available.
> In theory this is not necessary.
>
Fair enough.
>
> How the hub functions in a nutshell:
> - loads clients on startup (the xpl apps it serves)
> - listens on 3865
> - checks whether to accept from the source [V3]
This is the new IP check, yes?
> - checks incoming msgs to be valid xpl msgs
> - if it receives a HBEAT from a local IP, then stores the port nr in
> the clients list
> - broadcasts incoming msgs to all clients on the list
Should it also look at the target field, and filter based on that?
> - tracks HBEAT.END and expired clients
> - saves the clients when shutting down
>
> It doesn't send HBEAT items itself or doesn't listen to config items
for
itself.
>
It could though, couldn't it? Then the allowable IPs could be configured
via xPLHal.
Mal
xPL Main Index |
xPL Thread Index |
xPL Home |
Archives Home
|