I've been working with the ownet python access method to owserver for the past few weeks. In doing so, I became aware of the fact that a separate connection is opened to owserver for each operation (read, dir, write). This means that for even the simplest operation, 3 separate connections are typically required. For more complex operations the count goes up dramatically. Performing a scan for DS2401 devices on a hub branch requires at least 22 separate connections to discover two sensors.
How did this design of owserver come to be? There is a lot of overhead associated with TCP connection startup and shutdown. I don't understand why multiple operations could not be carried out over a persistent connection, eliminating the over head of all these connections. This also makes me wonder why there is not an option to use UDP as opposed to TCP. I didn't see any discussion of this in the archives (could have missed it I suppose). If this was a conscious decision, I'd like to understand the reasoning. I've been studying the owserver source, but I don't have enough of a handle on it yet to provide any insight into this. Comments? ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
