1 Mar 2005 11:51
RE: owserver changes
Christian Magnusson <christian.magnusson <at> runaware.com>
2005-03-01 10:51:21 GMT
2005-03-01 10:51:21 GMT
Hi Paul, I will think a bit on some different changes to owserver and do some tests here.... Another thing... I think I have used owserver in a wrong way most of the time... correct me if I'm totally wrong here... Do you know if there are any limitations on the outdevices today... I mean, should it be possible for many clients to connect to the same local port? It seems like there should be some kind of locking mechanism and idle-packets between the server and client to make sure not more than one client use a server connection. If the idle-packets stops, let say for 30 seconds, the server connection is marked as unused and some other can "login". I have sometime started owfs like this: owserver -d /dev/ttyS0 -p 3002 owfs -s 3002 /var/1wire owhttpd -s 3002 -p 3001 But I guess it should be like this instead... owserver -d /dev/ttyS0 -p 3002 -p 3003 owfs -s 3002 /var/1wire owhttpd -s 3003 -p 3001 I have noticed some strange behavior in the first case. When requesting some directories and files via owhttpd, it locks up but it continues to work if I kill owfs! It might be some bugs I have added to my local source here, but I just(Continue reading)
RSS Feed