Automatic [de]serialization

[michaelklishin]

It may be nice to steal a page from Hutch/etc's book and provide a way to serialize
and deserialize published messages and delivered bodies automatically. We can go
as far as having our own middleware (à la Rack or Faraday or Ring).

[owenthereal]

👍 This will definitely help my implementation as well: https://github.com/jingweno/message_queue/tree/master/lib/message_queue/serializers

[bobbytables]

👍

[camelpunch]

Link to book?

[michaelklishin]

@camelpunch Hutch is a project from GoCardless

[stefansedich]

I notice this has been sitting for a while, has there been any more discussion on this one behind the scenes? it is something I was wanting today so what better what to get what I want than to implement it.

[michaelklishin]

It needs to be opt-in, that's about as far as my opinion about this go. 

On 7 October 2016 at 10:31:48, Stefan Sedich ([email protected]) wrote:

I notice this has been sitting for a while, has there been any more discussion on this one
behind the scenes? it is something I was wanting today so what better what to get what I
want than to implement it.

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#185 (comment)

MK

Staff Software Engineer, Pivotal/RabbitMQ

[stefansedich]

Agreed, will have a think about it and see what I can come up with!

[tadman]

This would be nice especially if it was keyed to the Content-Type information provided as part of the message.

[mlh758]

Just came across this, I'd like to chime in on the "needs to be opt in" side. I have a couple subscribers that expect a string of bytes to do some initial processing, then deserialize the important bits.