I do not like the  /simultaneous/temperature interface.

As a general rule, owserver operations are synchronous: if you read say 
/uncached/10.AE9C54020800/temperature, you get a reply when the requested data 
is available.

On the contrary a write to  /simultaneous/temperature is asynchronous, since it 
will return *before* data is available.
IMHO for consistency also a write to /simultaneous/temperature should *block* 
until all conversions are performed. I.e. ‘simultaneous’ ops should be 
synchronous: by doing so there is no need for the 'sleep 1’ before the owread 
commands.

Moreover what happens if process A writes to  /simultaneous/temperature and 
process B reads from /uncached/10.AE9C54020800/temperature before the 1.0s for 
the conversion are over? Will this result in a race condition? Maybe all 
operations involving temperature should be blocked during the simultaneous 
conversion.

Finally we have different temperature resolutions.

/structure/22/temperature                't,000000,000001,ro,000012,v,'
/structure/22/temperature10              't,000000,000001,ro,000012,v,'
/structure/22/temperature11              't,000000,000001,ro,000012,v,'
/structure/22/temperature12              't,000000,000001,ro,000012,v,'
/structure/22/temperature9               't,000000,000001,ro,000012,v,'

which one will be returned by latesttemp? Wouldn’t it be better to have

/structure/22/last/temperature                't,000000,000001,ro,000012,v,'
/structure/22/last/temperature10              't,000000,000001,ro,000012,v,'
/structure/22/last/temperature11              't,000000,000001,ro,000012,v,'
/structure/22/last/temperature12              't,000000,000001,ro,000012,v,'
/structure/22/last/temperature9               't,000000,000001,ro,000012,v,'

instead of a catchall /structure/22/latesttemp ?
Even if the simultaneous conversion is valid for only a single resolution, I 
would still prefer a single /22/last/temperatureXX instead of a  /22/latesttemp 
node.
S.

> On 02 Feb 2016, at 01:18, Jan Kandziora <j...@gmx.de <mailto:j...@gmx.de>> 
> wrote:
> 
> Hi,
> 
> I just committed the "latesttemp" node we have been talking about
> recently. It's function: provide a way to read the temperature value
> from scratchpad *without triggering a conversion*.
> 
> This is especially useful in conjunction with simultaneous conversions.
> 
> $ owwrite /simutaneous/temperature 1
> $ sleep 1
> $ owread /uncached/10.AE9C54020800/latesttemp
>    19.6875
> $ owread /uncached/10.9EFD53020A00/latesttemp
>       21.5
> ...
> 
> Please pull from the git archive and test.
> 
> Kind regards
> 
>       Jan
> 
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 
> <http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140>
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to