From: Ron K. <ro...@za...> - 2001-03-03 20:46:15
|
No problem, I just want to make sure it wasn't a wrong configured MH. I can live with it... ;-) Ron. ----- Original Message ----- From: "Bruce Winter" <br...@mi...> To: <mis...@li...> Sent: Saturday, March 03, 2001 8:37 PM Subject: RE: [misterhouse-users] http_server time exceeded: time=3 > > Yep, unfortunatly, this is expected. When mh uses the CM11.pm to send X10 > data, it does a handshake to make sure all the data gets sent. Each X10 > command takes about .5->1 second, so if you have 3->6 house codes you are > turning on/off, mh will pause for 2->4 seconds. > > Most X10 events require just a few X10 commands, so it is not too much of an > issues. > > If this was a common and painful problem, one clunky way to work around > would be to run 2 instances of mh. One to server X10 data, and another to > do everything else, including send/receive X10 data from the first using > mhsend_server.pl > > Bruce > > -----Original Message----- > > When switching on or off 3 X10 lamps from a web url like: > > /SET?$All_lights?off > > I get this: > > 03/03/2001 14:14:17 : http_server time exceeded: time=3, header=GET > /SET?$All_Lights?off HTTP/1.1 > 03/03/2001 14:14:17 http_server time exceeded: time=3, header=GET > /SET?$All_Lights?off HTTP/1.1 > 03/03/2001 14:14:17 mh paused for 3 seconds > > Is this normal behavior? The swithing works ok. > > > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > |