Hello, I need to add AMQP 1.0 client-side support into an application but am
not having much luck.  I have been able to compile the AMQP 0.24 C++
org.apache.qpid.messaging.dll but it throws an exception when I use it in
the send/recv sample application.  I was also able to compile the Proton
library but it fails all 4 tests.  I would like to get some questions
answered which will help direct me as to what I should do next.  First off a
list of the requirements of the project I am working on;

1) The client is written in C#
2) The client will connect to an Apache based AMQP 1.0 (only) Broker
3) The client side needs to support failover (preferably in the AMQP
library)

>From what I have read both Proton and QPID 0.24 support AMQP 1.0.  That
said, when I build QPID 0.24 it tells me that it can't find Proton therefore
AMQP 1.0 support is not enabled.  This made me think I should just use
Proton.  If I go the Proton route I would have to implement my own C#
wrapper where QPID already has the C# wrapper.

A few of the questions I have are out of scope of this forum but I have them
included in case someone has the answer.  And here they are;

1) Given my requirements should I use QPID or QPID Proton and why?
2) If the answer is Proton, can I use SWIG to generate the C# interface to
Proton?
3) From what I read QPID has built-in failover to alternate brokers, does
Proton?
4) Can the Microsoft Azure Service Bus client be used to connect to an
Apache QPID AMQP Broker?
5) Does Microsoft Azure Service Bus client support failover to alternate
brokers?

Once I have an answer to the QPID vs QPID Proton question I will post
another thread that includes the output from CMake and Visual Studio.

Thank you.




--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Using-AMQP-1-0-in-a-C-application-tp7601072.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to