RE: [Project] RFC re Bulkhead (98k attachment)

["Broadfoot, Kieran J" <Kieran.Broadfoot@xxxxxxx>]

Keith,

Dont forget that HTTP is a transport protcol so we can throw just about
anything over it.  If we were going to be really flash we can filter the
data based on the receiving device.  All of a sudden we could end up
thinking of the lcd panel as a wap enabled browser.  If you think of it its
the same limited inputs and smaller screen size.  I dont see a problem
handing out wml or html, gif or wbmp depending on receiving device

just my tuppence.

kieran

-----Original Message-----
From: Keith Doxey [mailto:ukha@xxxxxxx]
Sent: Sunday, June 03, 2001 8:56 PM
To: ukha_d@xxxxxxx
Subject: RE: [ukha_d] [Project] RFC re Bulkhead (98k attachment)


Hi Keiran,

It looks good.

One thing worth considering though, you mentioned HTTP as an implementation
method. do you mean running a webserver on the device? If so, it might be
worth considering an option to run with pages optimised for 240x320
resolution.

This would allow a PDA such as iPaq, Cassiopia etc to directly access the
device using a wireless lan. This would mean that you could then have
something much cooler than a Pronto. A colour tochscreen remote contrl that
had full feedback from the devices it was controlling and you can do all
your email etc as well.

It would also give the kind of features offered by Crestron Colortouch
panels which cost a fortune. In fact, it would be better than a Crestron
because that has bitmaps stored in the panels and is limited in what it can
store/display. Pocket Internet Explorer can show you anything. Doorbell
rings, doorcam.jpg can be displayed on the iPaq. :-)

When accessing from an Epod, TV or PC the pages could then be optimised for
the optimal resolution of the viewing device.


Keith


-----Original Message-----
From: Broadfoot, Kieran J [mailto:Kieran.Broadfoot@xxxxxxx]
Sent: 03 June 2001 17:06
To: 'ukha_d@xxxxxxx'
Subject: [ukha_d] [Project] RFC re Bulkhead (98k attachment)



Everyone,

I know John and Keith have been very noisy with regards the minutae of the
UKHA project and to be honest they lost me pretty quickly.  However I know
some of you have shown an interest in helping with the software component.
So I think its time to see who wants to help out.  Having spoken
extensively
with John on this are current thinking is that quite possibly the protocol
between console and rabbit does not need to be complex.  One of the
features
of the rabbit is that its very easy to implement http and cgi and all of a
sudden it makes the complexity of the protocol much easier to handle.

Anyway we need to think about the console will know how to deal with each
device.  Should the user install some object code on the management code
that comes with the device or should we be a little more clever and allow
the system to self determine this?  I am quite tempted to suggest that we
payload into the rabbit a serialized java class detailing how to use the
device.  Its a simple task for a java app to read this object and handle it
correctly.  Anyone have any further ideas?

I made a bit of a start playing around with possible gui ideas this morning
and attached is a prototype.  You can ask for the code but I promise it
cant
do anything at all ;-)  As you can probably see its written n Java which I
like for its speed of development and multiple platform capabilities.  You
could even consider running a cut down non GUI version on a TINI or similar
acting as an embedded controller of the system.

Anyway if you have any thoughts/ideas/flames etc direct them to me ;-)

Enjoy the rest of the weekend.

Kieran




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/





Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/