What I did for something similar is to use Data::Dumper and write some Perl object into a file. The web-serving part reads that file and uses it to serve the page. I just check that the data structure I read makes any sense, and if not, I just re-read it, as it may have been read while the daemon was writing it anew. I realize this is very crude process synchronization, but if the updates are infrequent and the consequences would be to re-read the file, it makes it very simple.
On Nov 27, 2007 12:09 AM, Ryan <[EMAIL PROTECTED]> wrote: > I'm monitoring a laboratory scale through the serial port. Opening > that connection is expensive (I think) so I'd like to run a program > in the background that continually monitors the port and reports data > to my Mason site when it asks for it. What's my best solution? > > > Thanks! > > Ryan > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mason-users mailing list > Mason-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mason-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
