Searching hints for a web-app

Hi folks,

I don't if this is the right newsgroup for that question, if not pls. could someone guide me to the right one ;)

In my home, I have a computer sitting in the basement controlling all kinds of consumers in our house (lights, outlets - e.g. for TV, heater and so on). The switches in the walls do not switch the power, they just send singnals to the computer and that eventually (through a self-written program) turn on the consumers.
For that scenario I have also written a neat client application (C++) that shows on different tabs the top view for each floor (and the garage) - on those vies you can see all the different consumers (like bulbs or outlets) as icons. Clicking on them turns the consumer on/off - it reflects the state of the consumer by using different icons (bulb on, bulb off). The client is connected through CORBA with the server.
What I would like to do is, to come up with a web-based solution equal to that client. I think plain html drops out because it can not be notified when a consumer changes its state. The only two possibilities I can think of would be using Java-Applets or a flash animation. With the latter one I have no experience whatsoever, it is just a (uneducated) guess.

Anyone who could lend a hand on this project?

BTW: I could easely integrate a web server into the controller or run Apache on the same machine.

Thanks!
.

Relevant Pages

  • Re: Searching hints for a web-app
    ... self-written program) turn on the consumers. ... it reflects the state of the consumer by using different icons (bulb on, ... The client is connected through CORBA with the server. ... I could easely integrate a web server into the controller or run ...
    (alt.html)
  • Re: WSE interoperability with non .NET clients. Need help
    ... > security) that may be consumed by NON .NET clients. ... > possibility that some of the client consumers will be using VB 6, ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: XStream versus XMLEncoder
    ... *designers* of those classes is the concern that some client will, in fact, ... close that loophole so that consumers of the class need not concern themselves ... with it, nor risk the consequences. ... the client can ignore many threading issues and has no risk ...
    (comp.lang.java.help)