[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: Introduction
- Subject: RE: Introduction
- From: "Adam Stevens" <adam@xxxxxxx>
- Date: Tue, 26 Apr 2005 23:12:46 +0100
> > Certainly from what I've seen at xapframework.net a lot of
> effort has
> >gone into it.
>
> A few hours here and there, yes :-)
Looks like it!!
> It can be easier to get things up and running if the first
> xAPplication to start automatically takes on Hub duties, and
> that's the route that xAPFramework (xFx) employs.
Sounds like a good idea to me. Presumably then, a hub needs to first
check that there's not another hub running?! - Or, I guess if it can't
grab the port, it can assume there is.
> But, if you want to fiddle around a little, xFx-based xAPps
> can be configured to auto-detect the lack of a Hub or be
> forced into starting in either a Hub or HubClient mode
> because the Hub/HubClient protocol is built into xFx itself.
> This is up to the individual developer of course, but all of
> my non-dedicated-Hub xAPps definitely auto-detect their mode.
I'm really going to have to have a bit of a play with all this stuff!
:-)
A.
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|