> Windows Mobile 6.5 is based off of the Windows CE OS.  We ended up not using  
> AMQP and going with the Service Bus REST API.  We where having issues with 
> getting SSL working and also the mix of managed and unmanaged code. 
> 
> We do have plans at some point to develop a AMQP client library designed for 
> C# and compact framework. 
> 
> Cheers
> Ryan
> 
> 
> Sent from my iPad
> 
>>> On Nov 21, 2013, at 2:49 AM, "Gordon Sim" <[email protected]> wrote:
>>> 
>>> On 11/21/2013 04:42 AM, Ryan Finnesey wrote:
>>> If I wanted to send messages via AMQP from a Windows Mobile 6.5 device to 
>>> the Azure Service Bus would the qpid C library be the best option?
>> 
>> I'm afraid I don't know anything about Windows Mobile or its 
>> limitations, but in case it is useful here is a quick summary of the 
>> available clients at Qpid (that support AMQP 1.0, which you will need 
>> for Service Bus).
>> 
>> * The proton-c messenger client, which I believe has been tested against 
>> service bus and does work on windows. There may be an issue around ssl 
>> on windows(?) still.
>> 
>> * The qpid::messaging c++ client or the Qpid.Messaging .NET wrapper 
>> around it. This has been tested on windows, but not against service bus 
>> as far as I am aware. Unfortunately at present SSL does not work over 
>> 1.0 on windows.
>> 
>> * If you can run a JVM on Windows Mobile you could also use the 1.0 JMS 
>> client, or indeed the proton-j messenger, which is a java equivalent of 
>> the c based messenger.
>> 
>> Let us know how you get on with any of these that you try! If there are 
>> issues, hopefully someone here can help get them fixed. If they work for 
>> you that will be useful information for others in the same situation.
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 

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

Reply via email to