Re: xapFramework Hubs

["Michael McSharry" <mcs101main@xxxxxxx>]

------=_NextPart_000_0159_01C485E4.1867CCB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I reinstalled into separate folders and it is happier for the most part. 
T=
he GUI Viewer and Hub are working in hub mode.  The Hub Service was
already=
installed in its own folder so nothing changed there.  I can run without t=
he service so it is not important to fix.

The X10 connector will now show its popup messages

I did receive an error from the X10 connector that makes it unreliable for
=
real-world use.  After the error it no longer would send commands to the
CM=
11A, yet it still reported xap-x10.request messages.  "Exception in
Send Th=
read" "Specified Argument was out of range name: index"
The prior message with the same timestamp was 10 xmit house=3Dc unit=3D1. 
=
Some form of restart after failure would be nice or even on a failure to
st=
op sending heartbeats so the system has some indication that the service
ca=
n no longer be provided.
----- Original Message -----=20
From: Stuart Booth=20
To: xAP_developer@xxxxxxx=20
Sent: Thursday, August 19, 2004 10:51 AM
Subject: Re: [xAP_developer] xapFramework Hubs


On Thu, 19 Aug 2004 10:29:29 -0700, "Michael McSharry"
<mcs101main@xxxxxxx> wrote:

>I install all the xapFramework apps in C:\Program Files\XAP\  and unzip
=
them in a manner that retains the most current version of all the common
fi=
les.
> With this approach it depends upon upward compatibility for any
updates=
made.  Should I construct another folder layer and have multiple copies of=
these files loaded?

--

Ooo, yes, I think that might be worth a go. I tend to change things
around internally for newer versions of things as I see better ways of
doing something, adding new features, hoisting reuseable code out of
apps into the framework, refactoring bits of code in the framework
etc. Sometimes this involves deep rearrangement and I have to admit I
don't think about older versions much. I also don't tend to update
everything on the website each time I update something so there might
be wide variances. Viewer is definitely significantly updated over the
others.

I do try and retain compatibility so that other users won't be
inconvenienced, which should mean things are always upwardly
compatible. It's a great idea on the whole, and as things settle down
it certainly should be possible if it isn't already.

If I had some way of updating the phpNuke site programatically I could
have my web packaging tool update the site automatically which would
mean I would update the online versions more often and keep them all
in sync.

I'll try harder at upwards compatibility in future.

S
--=20
Stuart Booth <stuart@xxxxxxx>
xAPFramework.NET - a xAP software development framework for .NET

http://www.xapautomation.org/ 
     http://www.xapframework.net/