That seems to be one solution to the problem. We are really close to have children now (twins actually), so I doubt I will have time to do this myself right now. If nothing happens until Monday, we are going to the hospital to manually start it.
Until then I have lots of things to take care of at work, and I'm not sure if or when I have some spare time this week to do some programming. I guess we have to release a new version as soon as possible when this issue is fixed. /Christian On Tue, 2006-02-14 at 17:18 -0500, Alfille, Paul H.,M.D. wrote: > Ahha! I see your point. The delay waiting for the other thread is causing the > timeout. Perhaps a null message back while waiting would satify the problem. > > I think the strategy should be: > > owlib: > ow_server.c > loop on any "NULL" return messages from owserver > > owserver: > Each "handler" routine should start a second (ping) thread that sends a NULL > message every 1.5 seconds. > On handler success, kill the ping thread (but protect the actual message > sneding so that partial pings aren't sent) and return the real response. > > This way if we still timeout, owserver really has a problem and perhaps > "reconnect" should be done. > > Do you want to implement this, Chrstian, or should I? > > Paul > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
