i don´t remember but it´s something related to 'volatile' i don´t know if structure have it you want a more 'plug and play' solution at owserver right? i think it´s easy to implement (maybe it is implemented), must check with paul maybe just 'volatile' information on structure could help maybe a 'time' information about how volatile is the data should be nice? for example cached temperature - 30seconds? or something else... 0 = always volatile -1 = constant >0 = seconds to become volatile (cached values for example?)
2011/4/1 Vincent Danjean <vdanjean.p...@free.fr>: > On 01/04/2011 17:54, Roberto Spadim wrote: >> 2011/4/1 Vincent Danjean <vdanjean.p...@free.fr>: >>> On 01/04/2011 16:19, Paul Alfille wrote: >>>> Ok, the /structure directory returns a small text file for each >>>> possible property >>>> e.g. owserver --fake=10 >>>> owread /structure/10/temperature >>>> t,000000,000001,ro,000012, >>> >>> [ lots of very useful info ] >>> >>>> The fourth field is the read/write mode >>>> oo,wo,ro,rw >>> >>> what is the oo mode ? no access at all ? It is used ? >> >> maybe directory entry, must check owfs source code > > Directories appear as directories themself (so no info on them > can be get from /structure): > aya:/mnt/1wire# ls structure/1F/main > simultaneous thermostat > aya:/mnt/1wire# grep -r '^D' structure > aya:/mnt/1wire# > > The only occurrence of this mode is this one: > aya:/mnt/1wire# grep -r ',oo,' structure > structure/21/set_alarm/trigger:y,000000,000001,oo,000001, > aya:/mnt/1wire# > >>>> Does this expose all the data you need? >>> >>> yes, but the 'immuable' property : both 'temperature' and 'id' have >>> the 'ro' mode for 28* chips. >>> The idea would be to let know software using owfs that it can read this >>> value >>> only once and then catch it. >>> >>> So, my 'request' is nearly void. The only 'missing' thing (in addition to >>> the immuable information) for now is that I need to make two directory reads >>> to see the difference between plain and system files. But, as there is >>> catching, it is not a big deal. >> >> check ownet.php it have what you want (cache) > > ownet.php cache the structure information. But it is not what I want. > I want my program knows (without hardcoding it) that, for a DS18B20 sensor, > the 'id' property will never change (so, once read, it can be cached) but > the 'temperature' property (also ro) can change so the program must re-read > it when the value of this property is requested. > This information (will never change/can change) is not available (yet ?) in > the /structure directory. Perhaps a new mode (ri : read immutable) can be > added ? > > Regards, > Vincent > > ------------------------------------------------------------------------------ > Create and publish websites with WebMatrix > Use the most popular FREE web apps or write code yourself; > WebMatrix provides all the features you need to develop and > publish your website. http://p.sf.net/sfu/ms-webmatrix-sf > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers > > -- Roberto Spadim Spadim Technology / SPAEmpresarial ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
