On Nov 14, 2007 4:19 PM, Paul Dietrich <[EMAIL PROTECTED]> wrote: > Although by luck, none of the LLRP messages have two reserved fields, > vendor extensions (according to the schema) can contain more than 1 > reserved field. Do we need to document which of the reserved fields > this "override" affects? >
Ah, I see the problem now. I was thinking about message headers, but a similar attribute group is permitted in the parameter elements. I'll give it some thought. This override is for the message and parameter headers, not the body. Probably it should be named differently "HeaderReservedBits" for example. For the possibly many reserved fields in the body, I don't currently do anything with those. It would be nice and consistent to be able to specify values for those reserved fields. Probably it would have to be a list of optional reserved element at the spots where one or more reserved fields are allowed. Probably too complex to bother with but I'll think about it. -- 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
