Ok, I've been thinking about this one, and I think: first, the offset and length fields are good to have, yes? If they're not useful, then they should certainly not be included. But I think that for applications that transfer a lot of data, it will be useful, as you can use one large byte[] and don't have to either use small byte[]s for your main data buffer.
second, the default case should most certainly be that the user doesn't have to set either field (offset or length). To that end, I think that auto-setting offset and length when the setData() method is called is the 'right' thing to do. For users that don't care about offset/length, they don't do a thing - it's handled for them. For the few users that do want to set offset and/or length, all they have to know is they must set the offset and/or length _after_ the data, not before. That's not too bad, and it allows correct behavior in the default (i.e. 99% of the time) case. So...I'm going to update the Javadoc and default implementation to reflect this, unless there are comments. Everything's coming together I think, I'd like to put a 0.10 package out tomorrow or this weekend...so let me know if there are API comments (or RI comments, but the API is more important to get right at this point). Thanks. -- Dan Streetman [EMAIL PROTECTED] --------------------- 186,272 miles per second: It isn't just a good idea, it's the law! ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ javax-usb-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
