Skip to content

Different amqp handle props in different manner. #719

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
marhub opened this issue Jan 7, 2019 · 5 comments
Closed

Different amqp handle props in different manner. #719

marhub opened this issue Jan 7, 2019 · 5 comments
Labels

Comments

@marhub
Copy link

marhub commented Jan 7, 2019

Actual result:
in amqp bunny transport props are put into headers.application_headers
in ampq-lib transport, props are put into headers

Expected result:
I can see props next to headers, not injected into headers key.

If that's expected result - then someone can please explain me why?

@makasim
Copy link
Member

makasim commented Jan 7, 2019

This behavior is expected. AMQP sends properties as a special header called "application_headers".

@marhub
Copy link
Author

marhub commented Feb 4, 2019

@makasim Sorry, but you do not get me.

considering following code:

$headers = [
       'reply_to' => $replyToQueue->getQueueName(),
       'correlation_id' => Uuid::uuid4()->toString()
];
$message = $this->context->createMessage(
       json_encode($data),
       [], // props
       $headers 
);

when using Enqueue\AmqpBunny\AmqpConnectionFactory => message ( seems to be not ok ):

image

when using Enqueue\AmqpLib\AmqpConnectionFactory => message is different ( seems to be ok )

image

I expect them to be same in all implementations!

@makasim
Copy link
Member

makasim commented Feb 4, 2019

Agree, have you found out why this happens?

@makasim makasim reopened this Feb 4, 2019
@marhub
Copy link
Author

marhub commented Feb 11, 2019

I belive it's due to internal implementation of bunny lib

@makasim
Copy link
Member

makasim commented Feb 19, 2019

I belive it's due to internal implementation of bunny lib

closing than, should be addressed in bunny repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants