On Nov 14, 2007 3:21 PM, Christian Floerkemeier <[EMAIL PROTECTED]> wrote: > <!-- overrides for negative testing only --> > <xs:attribute name="Reserved" type ="xs:unsignedInt"/> > <xs:attribute name="Length" type ="xs:unsignedShort"/> > <xs:attribute name="TypeID" type ="xs:unsignedShort"/> > </xs:attributeGroup> > > Does the "<!-- overrides for negative testing only -->" comment in LLRP.xsd > imply that these attributes should actually not be used in LTK XML?
Getting to your actual question... The "negative testing" comment refers to the fact that these fields are only relevant at the binary packet level. LTK Perl will build messages with whatever value is provided if these fields are included. So if you told it to build a <ADD_ROSPEC> message you could alter the TypeID, or put a abitrary value in the Reserved or even change the Length to a bogus value. So for testing readers we actually do use them, and LTK Perl implements them. But a production client app would never use them. -- John. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
