Release Notes for 2.7p36

1. Include support from Egil Kvaleberg for the
   A. B1-R1-A Hobby Boards Barometer
       
http://www.hobby-boards.com/catalog/product_info.php?cPath=22&products_id=36
   B. S3-R1-A Hobby Boards Solar Radiation sensor
       
http://www.hobby-boards.com/catalog/product_info.php?cPath=22&products_id=82

2. Change threading model to allow owserver and owhttpd to run under OSX

3. Relax alias constraints in owserver
   Alias files can be specified for only the server and will propagate
back to clients.

-----------------------

Some explanation:

1. Egil included support (and man page updates!) for the sensors. He
uses default calibration values unless better ones are stored on-chip.
The sensors are based on the DS2438.

2. It appears that OSX doesn't like our use of condition variables.
The new model uses fewer threads, 'select' on the listening socket,
reference counting of the handler threads, and a pipe to signal the
last thread. The new model also waits for all the handler threads to
finish before exiting, which gives a small delay, but a more graceful
exit.

3. The alias names are human-readable names for the 1-wire slaves.
This worked well with a single process but got confused when there
were clients and owserver(s) involved. We now can handle the following
cases:
  A. If the client has the alias file, it sends the 1-wire address
rather than the alias to owserver.
  B If owserver has the alias file, an owserver presence query returns
the 1-wire address, so the client can add the alias locally.
  C. If the alias file is supplied to all the programs (say in a
configuration file) the view is consistent and continues to work well.
  D. Inconsistent alias files between client and server are not advisable.
  E. Light-weight clients (like owshell, ownet) treat 1-wire filenames
as opaque objects, and just send them to owserver unchanged. This
works with alias names, too.

------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to