Thank you, Robbie, for your answer. I will try to use it that way. What do you think about updating the docs to make it more explicit for not JMS users?
On Mon, May 11, 2020 at 4:20 PM Robbie Gemmell <[email protected]> wrote: > On Sun, 10 May 2020 at 19:19, Krzysztof <[email protected]> wrote: > > > > Hi, > > > > I'm trying to use the Closing Message Group feature using AmqpNetLite. In > > docs it is stated that I should set "JMSXGroupSeq" to -1. In AMQP > protocol > > it maps however to group-sequence property which is of unsigned long > type. > > To be clear it is of type sequence-no, which is [essentially] a uint > (not a ulong). > > > The question is: do we implicitly rely on ulong overflow to make this > > feature work? At least for amqp based clients of course. If any case, > > shouldn't we update the docs to make it explicit? > > > > For the AMQP JMS mapping we defined that group-sequence uint values > 2^31 to 2^32 - 1 were mapped to JMSXGroupSeq signed int values -2^31 > to -1. > > i.e basically the uint 2^32-1 would become the -1. >
