Re: Re: xAP / xPL Gateway

[Ian Lowe]

----- Original Message -----
From: "mark_harrison_uk2" <<a
href="/group/xAP_developer/post?postID=ZEUuWCcwGfqZzFVbLqPz8SrvU7tMo9C_L3bUEBVh5ILbmjd3cH3uRvfHzVWYRYR8Zo4frRy_aqUvE_8">mph@a...</a>>
>
> --- In <a
href="/group/xAP_developer/post?postID=ioS6nO7X8QQcNI1HgK7FPWIY9nueO_m-W831dJ8Dy6KEAO9WKM9Z7x4mCi_plhlhKBcUbiKXfCCCgD5kczhCY-g0Cw">xAP_developer@xxxxxxx</a>,
"Ian Lowe" <ian@w...> wrote:
> > ----- Original Message -----
> > From: "Stuart Booth" <lists@x...>
>
> > From an end user p.o.v. mucking about with "this app can be
a hub",
> > or "this is a hub app" etc, is (imo) just too much
hassle.
>
> Nooo.. It's all auto-detecting in Stuart's framework.
>
> The end user simply runs the apps (s)he wants.
>
> The first one to start sets itself up as a hub. The rest detect it
> (whether they're Stuart's or not) and use it.
>
> Zero configuration for user. The user doesn't even realise this is
> going on.

Ah, I got the impression that we had a few different hubs?

As long as all of the applications behave in this well-formed way, it
should
work fine. As xPLHal starts as a windows service, it will be running long
before anyone gets to the running applications stage, so each of the xAPps
launched by the end user will just detect the hub and go..

Remember, this is for the server running xPLHal only: it doesn't apply to
any other machine running xAP on your network. As far as I can see, this
won't change anyone's behaviour or experience.

I.
I.