On Thu, Jan 2, 2014 at 10:31 PM, Colin Reese <[email protected]> wrote: > My current approach is to separate client/database and server/database > interactions. A client can still force a read if they wish. It's essentially > a cache, but I use it generally for all io, not just owfs. Logging just > automagically works using the read daemon that updates the database. It also > has the benefit of synchronizing readings if you wish. Good for process > control.
If I understand you correctly this is what saal does as well. A daemon is always running pushing reads into the database and then clients read the most recent value from the database. For actuators clients currently issue commands directly but this is not ideal for the disconnected use case. I'll have to actually do client -> server -> actuator so that the server buffers the command for the next time the actuator is available. Pedro ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
