Re: Vote time and question...

[mark_harrison_uk2]

--- In <a
href="/group/xap_automation/post?postID=edT_2RE5dVxYGT-g_u2IxzbGeSwjEAOZqSazBkj1ojTdnXljDvzEm8GqrpzYL4ruGc3p66f4ubNQTRL_yGwE3eUkUy16bh4">xap_automation@xxxxxxx</a>,
James <james@m...> wrote:
> A) TCP router for xAP messages to another network

I think that this already exists?

> B) Jabber messaging interface ( jabber allows routing to msm,icq,aol
> etc)

YES, YES, YES.

> C) Some kind of graphical xAP display inc. screensaver for point510

Would be good.

> D) A central brain like xPLHal

I think that one of the huge long-term advantage of xAP is that it
lends itself to more intelligence being pushed out to end-node
devices. For example, the hi-fi can mute _directly_ in response to
the "phone's ringing" even, with the "brain" acting as
an INSTALLER
tool to set up this intelligence, rather than something that is left
running all the time.

That having been said, lots of people like central controllers... so
go for it... However, any architecture that allowed a "compile
configuration out to remote devices" type approach in the future
would be a much more powerful product for me.

Of course, this raises all kinds of questions about configuration
description languages :-)

Regards,

Mark