Am 05.10.2015 um 14:23 schrieb Alex R. Gibbs:
>
> However, other clients will have to wait if they happen
> to query owserver during the conversion/read.
>
No. That can only happen if you use parasite powered sensors. Because
parasite power occupies the bus during temperature conversion for
powering. That's a limitation of the hardware, you cannot do anything
about that.
With powered sensors, a client will only have to wait
* if the particular sensor value is marked invalid, that is because
conversion on that sensor was never triggered or the last result was
already read out
* if the particular sensor is currently at conversion stage and you are
reading uncached.
If you take the three precautions - powered sensors only; continously
trigger conversions within half the cache timeout, preferably
simultaneous ones; read cached values only - clients will never stall.
> I was thinking that if a
> conversion or read is in process
>
That is only a problem when you are using parasite power.
> and the cached value hasn't expired that
> owserver could immediately return the cached value instead of making the
> client
> wait. That way no client would ever have to wait as long as something is
> triggering conversions. That would keep things relatively simple.
>
It is as simple as I have written. Just use that one-line-script I've
posted and owserver will behave exactly like that.
Kind regards
Jan
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
