The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: (OT)Virtual co-driver with a seventh sense


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OT: Device control and status display using Pocket IE


  • To: ukha_d@xxxxxxx
  • Subject: Re: OT: Device control and status display using Pocket IE
  • From: "Patrick Lidstone" <patrick@xxxxxxx>
  • Date: Wed, 30 Jul 2003 14:06:11 -0000
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx


> My problem is implementing a 'real time' status display via simple
HTTP or
> Java script,  update at say once per second.
> We need to be able to display some very simple parameters, status,
> temperature etc.  as a dynamic display that updates in the browser
window.
> I'd like to keep flicker/refresh to a minimum so I don't really
want to
> update the whole page.
> My first thoughts are to update a 'status' frame, or to use Java
script to
> fetch values from the web sever by intercepting requests for
specific
> pages/CGI.
>
> Anyone got any thoughts or preferably and code examples so that I
can show a
> proof of concept to the guy's that will eventually implement this?

HTTP really isn't the right tool for the job in this environment IMO -
it doesn't do any form of push very well.

I've written a xAP active X control for PPC, which can be used with
Embedded VB (which is a free download from MS) to effect bi-
directional, real-time control. Unfortunately it's not very stable,
but it might be worth a look. Even if you didn't go the xAP route,
you should be able to hack together something in VB using
conventional sockets which will have much better usability than a
browser based solution.

Patrick



Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.