Hi, I've noticed that for some USB error, such as resetting the USB port, then Barry wouldn't notice the error has occurred. I tracked this down to Barry ignoring zero size reads, so I fixed that (5bc30ce911ac3fb0b839) but then discovered that if a usb error had been seen then Socket::Close would hang on wait_pop while trying to receive data, so I made DefaultRead return immediately if a usb error has been seen (a41446a2ac3d9f96d859).
I considered the alternative of having the Socket::Close use the device timeout, but I didn't see any benefit to this and it would just cause the user to wait for longer before the socket was closed. Does this seem fair? (There's one other minor change in my branch at git://github.com/tobygray/barry.git to remove an implicit magic constant from a select call in the raw channel tool). Regards, Toby ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
