We're using your library to read registers off one of our appliances and notice that sometimes we get issues because the library assumes responses received from requests are in the same order -- we're not sure if it's a library problem or a user-of-the-library problem. Here's how this problem occurs.
This code works fine until the following happens:
What's happening according to wireshark is we send read requests for our 3 registers, then in black, you can see we get a response back for the VO_ERX register, while the respone the library was expecting to receive first is in blue (VO_ERR). This happens only sometimes, but when it does, we see the following (note that this isn't the error from that specific wireshark capture but the same assert always fails):
Hello,
We're using your library to read registers off one of our appliances and notice that sometimes we get issues because the library assumes responses received from requests are in the same order -- we're not sure if it's a library problem or a user-of-the-library problem. Here's how this problem occurs.
At a high-level, this is what we're doing:
This code works fine until the following happens: What's happening according to wireshark is we send read requests for our 3 registers, then in black, you can see we get a response back for the
VO_ERX
register, while the respone the library was expecting to receive first is in blue (VO_ERR
). This happens only sometimes, but when it does, we see the following (note that this isn't the error from that specific wireshark capture but the same assert always fails):I'm not sure if we're using the wrong abstraction (i.e. using
proxy
) or if the library must have these responses appear in order. Any ideas? Thanks!