On 24/09/2010 21:45, Chris Frey wrote: > > I saw your messages on libusb as well. This is useful information. > > In reading your responses, I'm thinking that all we really need to know > is whether a 0 size packet is valid for the *Blackberry*. And to my > knowledge, there is never such a packet in its communication. > > In this case, I like the idea of a totally separate exception, with some > logging, so that if it ever does encounter a 0 size packet, it will be > obvious, recoverable, but also debuggable. :-) If this behaviour is > easily configurable too, that would be even better, so that if something > goes amiss, we can ask users to test both easily in the field. > > Does that make sense to you? Yes. Seems entirely reasonable. I'll add a new exception deriving from Barry::Error for zero length reads. Do you think it should be a more general short packet exception and also capture the read being less than sizeof(pack->socket) case?
My initial feeling was to treat both cases the same, as there's clearly something we don't understand going on, so it's probably best to get a bug reporting that Barry doesn't work than to carry on. However I'd be happy to continue the current behaviour of just skipping packets of 1 byte length. 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
