Extract event format mapping from AMQP module
Reported by John Wright | October 24th, 2011 @ 01:13 PM | in 1.0 (closed)
The AMQP module uses a plugin-style design, with Spring XML files (named by convention) that load in the required message-translating code.
The downside of this approach is that a custom build of Diffa becomes necessary. A cleaner separation can be achieved by splitting message translation code out into a proxy. The proxy will listen for messages on given queues, translate them, then forward them on to Diffa in the standard JSON wire event format.
Comments and changes to this ticket
-

-

Ben Hood November 1st, 2011 @ 02:39 PM
- Milestone set to 1.0
- Milestone order changed from 16 to 0
-

Ben Hood November 1st, 2011 @ 02:59 PM
- Milestone order changed from 2 to 0
(from [c6174d1767ec40c83e757df5c656e74722ab8002]) [#397] Added some success typing https://github.com/lshift/diffa/commit/c6174d1767ec40c83e757df5c656...
-

Ben Hood November 1st, 2011 @ 03:29 PM
(from [232aa1e0947ef6cb121255f61aea915652f3ced3]) [#397] Cleaned up some more event format mapper back references https://github.com/lshift/diffa/commit/232aa1e0947ef6cb121255f61aea...
-

Ben Hood November 1st, 2011 @ 04:07 PM
(from [47846653054e73d1240fa0773b896b74cfbdac60]) [#397] Deleted inbound content type attribute https://github.com/lshift/diffa/commit/47846653054e73d1240fa0773b89...
-

-

Ben Hood November 1st, 2011 @ 11:13 PM
(from [dfd1a0cbb5fd90e6542f2b98e873a614c32662e1]) Merge pull request #100 from lshift/397
[#397] Remove old event formatters https://github.com/lshift/diffa/commit/dfd1a0cbb5fd90e6542f2b98e873...
-

Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
People watching this ticket
Referenced by
-
398
Allow multiple change events in the same message via AMQP
This ticket is effectively a sub-task of #397 - the
exist...