Response to GET:QUEUED MESSAGE when NACKing query - E1.20 RDM (Remote Device Management) Protocol Forums

prwatE120 · February 24th, 2016

I have also coded along the lines that Eric has, and reply with QM as the PID in the NACK.

We might all think it is logical, but it is not defined behaviour as per the E1.20 document, which states the response to a QM shall be a STATUS_MESSAGE response.

10.3.1 "A responder with no messages queued shall respond to a QUEUED_MESSAGE message with a STATUS_MESSAGES response. "

Where do we state that this does not apply to a NACK from a responder with no messages queued ?

Are we happy to allow either PID in NACK responses, and add this behaviour to an E1.20 erratta ?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
E1.37-1 RDM Message Extensions document in Public Review	sblair	RDM General Implementation Discussion	2	December 13th, 2010 03:11 PM
Status Message Markers	hamish	RDM General Implementation Discussion	4	December 9th, 2010 11:12 PM
Additional Status Message ID request?	berntd	RDM General Implementation Discussion	3	October 28th, 2009 07:28 PM

February 24th, 2016	#1
prwatE120 Task Group Member Join Date: Jun 2006 Posts: 181	I have also coded along the lines that Eric has, and reply with QM as the PID in the NACK. We might all think it is logical, but it is not defined behaviour as per the E1.20 document, which states the response to a QM shall be a STATUS_MESSAGE response. 10.3.1 "A responder with no messages queued shall respond to a QUEUED_MESSAGE message with a STATUS_MESSAGES response. " Where do we state that this does not apply to a NACK from a responder with no messages queued ? Are we happy to allow either PID in NACK responses, and add this behaviour to an E1.20 erratta ?