On 05-07-09 14:03, Paul Alfille wrote: > Nice graph. You are monitoring car engine parameters?
mini tractor-puller with car engine http://www.minimumrisk.nl/?lng=en > There is one other design alternative (which is sort of suggested by your > note). > > Currently each cache item starts its timeout from the time it was > actually measured. > > We could start all the volatile timeouts from a common time, so they > would all expire at the same time. > That would give the behavior you want. It would be less precise, but > more automatic than having a cache purge switch. That would be very nice but if I want to use the volatile timeout it would require shorter times then one second too. Apart from that changing the behaviour of owfs could make other projects stumble due to changes... U told me some while/threads ago to use a polling script to refresh the cache and read the cached data. This weekend I tested a threathed script which polled all the uncached sensors at once every 0.5 seconds and wrote the data to an alternative cache mirror after doing calculations. This setup doesn't require owfs to be modified and fills my cache dir with fresh and modified (rpm calculation, pressure calc. from volt sensor) data which is refreshed every 0.5 seconds. That data is read every second and written in mysql and it seems that it works fine, will test that next week and see if shorter times will work too (0.2 or 0.1 seconds)... ------------------------------------------------------------------------------ _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
