Howdy LTK folks,
This is about adding responseType to llrpdef.xml.
This jist of the problem: LLRP does not have
any implicit clues to indicate for a given
request message (GET_READER_CAPABILITIES)
which message type is the response
(GET_READER_CAPABILITIES_RESPONSE).
In LKTC[PP], there are calls that look like this:
pResponse = Transact(pCommand,
&typeDescriptorForResponseType);
It would be oh so so much nicer if it could look like this:
pResponse = Transact(pCommand)
and there was enough information within LTK that Transact()
can determine the response type itself.
Hence:
<messageDefinition name="GET_READER_CAPABILITIES"
...
responseType="GET_READER_CAPABILITIES_RESPONSE"/>
...
</messageDefinition>
or
<messageDefinition name="GET_READER_CAPABILITIES ...>
<responseType>GET_READER_CAPABILITIES_RESPONSE</responseType>
...
</messageDefinition>
further
<customMessageDefinition name="ACME_EXTENSION" ...
responseType="ACME_EXTENSION_RESPONSE">
Thoughts?
Regards,
-gww
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
