[
https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61187#action_61187
]
Jim Gomes commented on AMQNET-271:
----------------------------------
Instead of a callback interface style of programming, wouldn't it be more
.NET-like to use an event driven architecture? For example:
The IMessageProducer interface would support a PreSendMessageEvent that could
be used to register an event handler for processing the message. Likewise, the
IMessageConsumer interface would support a PreDispatchMessageEvent event. This
would make implementations cleaner and simpler, by creating a separation of
concerns. The implementor would not be forced to implement both transforms,
since they could create event handlers individually in case they only want to
handle pre-dispatch events and don't care about pre-send events.
Just trying to understand this feature a bit more.
> Add support for a Message Transformer to be set in NMS API
> ----------------------------------------------------------
>
> Key: AMQNET-271
> URL: https://issues.apache.org/activemq/browse/AMQNET-271
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ, EMS, MSMQ, NMS, Stomp
> Affects Versions: 1.3.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.4.0
>
>
> Add support in the NMS API for users to set an custom MessageTransformer on
> the NMS object:
> IConnectionFactory
> IConnection
> ISession
> IMessageProducer
> IMessageConsumer
> The transformer would be an instance of IMessageTransformer which provides
> two methods:
> {noformat}
> /// <summary>
> /// Interface for a class that can Transform a Message from one type to
> another either
> /// before consumption or before sent by a producer.
> /// </summary>
> public interface IMessageTransformer
> {
> /// <summary>
> /// Called from an IMessageProducer prior to sending the IMessage,
> allows the client
> /// to perform a transformation on the Message prior to it being
> sent. This allows a
> /// client to configure a single Producer to convert a Message to a
> format that can be
> /// processed by a specific receiving client.
> /// </summary>
> IMessage ProducerTransform(ISession session, IMessageProducer
> producer, IMessage message);
> /// <summary>
> /// Called from an IMessageConsumer prior to dispatching the message
> to the client either
> /// by the 'Receive' methods or from the async listener event.
> Allows the client to perform
> /// message pre-processing before some messages are dispatched into
> the client code.
> /// </summary>
> IMessage ConsumerTransform(ISession session, IMessageConsumer
> producer, IMessage message);
> }
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
