On Monday 13 February 2006 12:28 pm, Christian Magnusson wrote: > The problem is in ow_server.c:ServerDir() (for example) where ToServer() > usually returns VERY quick and the request is put in a queue to be executed > on the remote-server. > > If there are 10 different read requests to > /1wire/uncached/10.xxxxxxxxx/temperature from 10 different remote-clients, > then it could take 10 seconds before FromServerAlloc() return the first row > in a directory listing. > > I can't see any possibility to keep the timeout here... The only > possibility would be to add a timeout around connect() and eventually abort > the sequence before sending the command too the remote-server. The read and > write commands should timeout by itself and return -1 upon failure. > > Do you agree? > > /Christian
Let me test. In theory, the dir listings are returned one entry at a time, so shouldn't have the full latency. I wonder if 2 seconds would be sufficient? Paul Alfille ------------------------------------------------------- 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 Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
