Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
From: =?utf-8?Q?Michael_Andr=C3=A9_Pearce?= <michael.andre.pearce@me.com>
Content-type: multipart/alternative;
 boundary=Apple-Mail-16412FA3-3B52-4539-B538-15E879C955C9
Content-transfer-encoding: 7bit
MIME-version: 1.0 (1.0)
Date: Wed, 31 May 2017 03:08:15 +0100
Subject: Re: [DISCUSS] Custom Object Serialisation Support
Message-id: <58D5BCCF-16B8-4C4E-BB2F-04F12D8E7DAA@me.com>
References: <95C56966-F848-47A0-B587-9F0E9AAE06F9@me.com>
 <1D42C4DB-B265-40FA-8C50-80423BC81289@gmail.com>
 <984A9C1D-72E2-4B62-965C-374C407A45EB@me.com>
In-reply-to: <984A9C1D-72E2-4B62-965C-374C407A45EB@me.com>
To: dev@activemq.apache.org
archived-at: Wed, 31 May 2017 02:08:25 -0000

--Apple-Mail-16412FA3-3B52-4539-B538-15E879C955C9
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Or even (as we use address now)

> byte[] serialize(String address, Object o)
>=20
> Object deserialize(String address, byte[] bytes)


Sent from my iPhone

> On 31 May 2017, at 03:00, Michael Andr=C3=A9 Pearce <michael.andre.pearce@=
me.com> wrote:
>=20
> Hi Matt,
>=20
> I think having just a SerDe interface for payload handling separate from a=
 general interceptor / client side plugin, is beneficial as then it keeps th=
e logic for serialsation well encapsulated. And also cleaner if we need to d=
o anything (eg sending it as a bytesmessags with a header flag)
>=20
> I see this very much like difference in kafka where you have payload seria=
lisation (serdes) and custom-plugin (interceptors)
>=20
> Also having just a serde makes interface for people to implement and care a=
bout much simpler. Eg this is almost the interface I would expect:
>=20
> byte[] serialize(Destination destination, Object o)
>=20
> Object deserialize(Destination destination, byte[] bytes)
>=20
> Nice and simple to implement without having to care about anything else.
>=20
> Cheers
> Mike
>=20
>=20
> Sent from my iPhone
>=20
>> On 30 May 2017, at 23:18, Matt Pavlovich <mattrpav@gmail.com> wrote:
>>=20
>> Michael-
>>=20
>> +1 dealing with bytes messages is preferred to object messages and custom=
 object SerDes is super useful.
>>=20
>> What do you think about considering a generic client-side plugin approach=
 vs just a payload handler?=20
>>=20
>>> On May 30, 2017, at 4:03 PM, Michael Andr=C3=A9 Pearce <michael.andre.pe=
arce@me.com> wrote:
>>>=20
>>> If present then this would be used to serialise the Object instead of th=
e default, and subsequently create/convert to a BytesMessage, with a header s=
et to denote it was custom serialised.
>>=20

--Apple-Mail-16412FA3-3B52-4539-B538-15E879C955C9--