I'd exercise the persistent TCP option, but I need a new build for the NSLU2. Real Life(tm) has not allowed for any owfs time in the last two weeks or so, sorry about the lack of updates. I've got ownet python module templates for the new read directory function and the persistent TCP connections, but don't have any way to test. (I still don't have a NSLU2 build environment set up so I haven't been able to build a new owserver.) Should be able to make some progress this weekend if I can find accurate instructions on setting up the build environment.
Paul On Thu, 25 Jan 2007 21:47:56 -0500, "Paul Alfille" <[EMAIL PROTECTED]> wrote: > Found the problem -- it was in swig.i uu unsed by owperl, pwpython and > owphp. Fixed in the CVS. > > I'm working on some "simultaneous" bugs that Chrstian found, then we'll > make > a new release. > > Peter, have you looked persistent tcp connections? The strategy is to set > the persistent bit in the SG parameter of the message, and if it is > returned > set, keep the same file descriptor open for the next message. If the next > message fails, close and open a new descriptor and try sending again. The > connection may have timed out. > > It's implemented in the perl module: OWNet.pm > > Paul Alfille > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
