You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Asankha C. Perera (JIRA)" <ji...@apache.org> on 2008/01/07 07:05:34 UTC
[jira] Updated: (SYNAPSE-223) AMQP Transport
[ https://issues.apache.org/jira/browse/SYNAPSE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera updated SYNAPSE-223:
--------------------------------------
Fix Version/s: 1.2
> AMQP Transport
> --------------
>
> Key: SYNAPSE-223
> URL: https://issues.apache.org/jira/browse/SYNAPSE-223
> Project: Synapse
> Issue Type: New Feature
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 1.2
>
>
> The AMQP transport will be based on the Apache Qpid project.
> Apache Qpid has a JMS client implementation over AMQP. Since Synapse has a JMS transport, you could use that to get AMQP support as well.
> However a native client has the following advantages.
> * You can use any exchange, not just direct (JMS Queues) or topic (JMS Topics). Ex. fannout, headers or a custom exchange.
> * Ability to customise the exchange type, exchange name, routing key and other AMQP specific parameters.
> * More fine grained control of AMQP concepts
> * Possibility of streaming large attachments off the disk. (need to figure out how to leverage the AXIOM support here).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org