[
https://issues.apache.org/jira/browse/AMQNET-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-201:
-----------------------------
Component/s: (was: NMS)
WCF
> WCF binding to support request reply message exchange
> -----------------------------------------------------
>
> Key: AMQNET-201
> URL: https://issues.apache.org/jira/browse/AMQNET-201
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: WCF
> Affects Versions: 1.1.0
> Reporter: Mark Pollack
> Assignee: Jim Gomes
> Priority: Minor
>
> I remember a while back there was some discussion on a JIRA issue where there
> was an explicit decision not to implement the request reply message exchange
> pattern in the WCF binding. I think this is not the correct decision.
> Request/Reply is a natural interaction for messaging systems, though clearly
> not the default. Implementation options are to use a temporary queue as the
> return destination or to setup a standard queue but create a message listener
> with a selector. Just for reference the TIBCO WCF binding supports request
> reply message exchange. A customer driven motivation behind this is that
> usually everyone creates request/reply endpoints over http transport in WCF.
> When they want to switch transports to messaging they discover (in MSMQ case)
> that they can't and would have to redesign their entire web services design
> to accomodate using JMS transport. This is simply not needed. Please
> reconsider and let's discuss more.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
