On 5/25/09, Steinar Midtskogen <[email protected]> wrote: > I've written a C program using owcapi, which makes an Oww like log > file by accessing several owservers. The idea is get several > sources into one log file and one offline source is not to affect > logging from the other sources and have owserver to all the low > level stuff. > > It works this way: > * Fork off a new process for every owserver. > * In the new processes make a thread for every value to be logged > which simply reads and store the value at its own pace (typically > every 10 seconds). > * When it's time to write to the log file, the parent will cancel > all the threads, process all data from every thread (average, max, > min, whatever to be logged etc) and log to file. > > It will produce quite a few owserver requests, but hardly more than > a few per second and most will be for cached values. Should this > cause any problems for owserver? The program causes owserver to > fork into many processes (in this setup, about 15), but that > shouldn't be a problem. > No problem for owserver. There are protections (locks) against conflicting requests, and the program has no intrinsic limits on threads or requests.
------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
