The creation field might not fit into one byte which makes the PID_EXT format unsuitable for this case.
The NEW_PID_EXT format is supported since Erlang 19.0, so it is safe to always use it, no matter the value of creation, because modern RabbitMQ 3.7+ versions require at least Erlang 20.3+.
The
creation
field might not fit into one byte which makes thePID_EXT
format unsuitable for this case.The
NEW_PID_EXT
format is supported since Erlang 19.0, so it is safe to always use it, no matter the value ofcreation
, because modern RabbitMQ 3.7+ versions require at least Erlang 20.3+.References #313.