Hi, I finished the transition from using owfs vs. directly interfacing owserver over the network. I have been running my setup for over 4 weeks with rather heavy loads (1 Hz read/write activity on 26 1-wire devices) and feel that some preliminary conclusions can be drawn.
- This setup seems much more stable compared to the owfs based setup. I have not seen a single read/write failure over the 4-week period - The client is written in a way that it simply retransmits the request to owserver upon i.) error returned or ii.) lack of response whithin 6 seconds, hence is not subject to file handling exceptions. If the latter occurs it stops/starts the owserver, which is eventually encapsulated into a system service - Although it is more stable by design the bottomline is that I have seen neither errors occuring during the 3-week period, which normally happened with the owfs approach The conclusion is that I do not recommend the owfs approach for heavy applications. It has many layers where the root cause could be including fuse itself or the owfs specific code and appears so seldom that is very hard to debug. Doma ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
