On 16/06/2020 8:46 am, Ivo Wever wrote:
Hi,
I'm trying to interact with an AMQP endpoint using the Ruby
implementation. The endpoint is very specific in requiring a ulong
message id, even though the message id they want is 1 [1]. However if I
set it to 1 using Ruby, it is sent as a smallint (verified using
wireshark), which they reject.
That sounds like a bug in the ruby wrapper code. I assume this is for
the proton API?
The python equivalent has an explicit test for a numeric value which it
then ensures is a ulong. I don't see anything equivalent in the ruby
(but I'm not that familiar with that binding).
Arguably the c library should not emit invalid AMQP but I don't think
there is any check at present.
I've looked into the SWIG automatic conversions and the other
encoding/conversion code, but I'm unclear in how I can get the message
id to be a ulong with the value 1.
What would be ways to achieve this?
[1] I know it should be unique, but it's not under my control
thanks and best regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
