Re: EPP Poll 'msgid' attribute

Mike,

If you are creating a different type of queue that is not FIFO I suggest
that you create a new object mapping (e.g. Selectable Queue Object
Mapping) that would provide the interface that you're looking for and to
keep the FIFO queue support as defined by RFC 5730.  Changing the
semantics of existing mature interfaces for a new purpose would be an
interoperability issue that is highly discouraged.

--


JG



James Gould
Principal Software Engineer
[email protected]

703-948-3271
21345 Ridgetop Circle
LS2-2-1
Dulles, VA 20166

VerisignInc.com




On 10/31/11 5:33 AM, "Mike O'Connell" <[email protected]> wrote:

>Hi All
>
>
>We're currently implementing an EPP based registry.
>
>One of our test registrars pointed out something of interest which I
>thought should be mentioned in the spec.
>
>The EPP schema element for 'poll' requests allows for two attributes 'op'
>and 'msgid'. The spec states that when op='req' is used the server should
>return an unacked item from the FIFO queue, and that when op='ack' is
>used you need to specify the 'msgid' to acknowledge.
>
>We're looking at implementing a selectable poll message process where the
>op='req' can specify the clTRID as the 'msgid' attribute to retrieve any
>unacked responses associated with that client identifier.
>
>Has anyone implemented anything like this? What are the thoughts
>regarding this?
>
>Kind Regards,
>
>
>Mike O'Connell
>Domain Name Services
>
>
>_______________________________________________
>provreg mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/provreg

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg