Casey,
we are now setting the version by default to 0x1.
In the next version of llrpdef.xml, we might want to add an
element/attribute that specifies how the binary encoding of the version.
This avoid hard-coding a default value in the code or having a table in the
code that maps llrpdef.xml version numbers to binary encodings.
- Christian
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Casey Hagen Sent: Montag, 25. Februar 2008 19:51 To: [email protected] Subject: [ltk-d] Java LTK setVersion on messages Hello, I have built the java LTK and I am now starting to test it, but I have a few questions. Why do I have to set the version on every message? Is there an easier way to do this, or why cant the toolkit set the version when building the jar? Also, there is a small bug with the BitList(string) constructor, if I create a new object with BitList(001) and then call setVersion with the bitlist object, setVersion throws an exception saying wrong length of version. Thanks, Casey _______________________________ Casey Hagen | Field Applications Engineering Program Manager 701 N. 34th Street, Suite 300 Seattle, WA 98103 [EMAIL PROTECTED] Desk: 206.834.1093 | Cellular: 206.295.5637 http://www.impinj.com/
<<image001.jpg>>
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
