Code duplication inside messages

[php-enqueue]

Code duplication inside messages

[makasim]

That true, but I do not want to couple transports in any way. and I do not want to put more stuff to psr-queue lib.

[Koc]

It is ok put some common implementations to psr-layer. Something similar available for cache https://github.com/php-fig/cache-util/tree/master/src

[makasim]

Let's try it then.

[Koc]

Does messages implementations is different for different transports? Message is like value object, similar to cache item.

[makasim]

They are different. It may have additional stuff to what it the message interface require.

For example. AMQP message has a delivery tag which is used while ack\reject.

[bendavies]

https://www.sandimetz.com/blog/2016/1/20/the-wrong-abstraction :-)

[makasim]

Yeap, that's my favorite.

[makasim]

DRY is not a silver bullet and could do harm as well

[makasim]

I give it a thought and me decided not to introduce a trait. There are the reasons:

1. The most important. If we do a change in the trait because we need it in AMQP but at that time it breaks another Message from completely different transport.
2. We remove duplication in easy to use and understand the code. Almost getters and setters
3. The code is not expected to change often.

The solution: Provide a spec test case for messages so every implementation could be tested against it. This is addressed here: https://github.com/php-enqueue/enqueue-dev/pull/102/files