Recv_async_msg questions

As far as I can tell, EVENT_CODE_SUCCESS (Defined as success: a packet
was successfully transmitted) events never seem to happen. That’s okay
with me and I’d worry about the bandwidth they’d take if I were
transmitting and receiving at the same time. Are they just not
implemented, yet?

I need to start and stop transmitting, do some work, and go around
again. I think I’m seeing residual events after I end a burst. Should I
use the metadata’s timestamp to filter them out or is there a way to
flush the queue of events?

-Marc

I envisioned a way to send a burst with a request to ACK. If you enabled
the ACK, you would expect a async message to come back either one of the
errors or a success. This is not implemented.

-Josh

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs