I know this post is a bit dated but I wanted to see if Cliff or Mike moved forward with the port to CE? It would be very helpful to a project I am working on.
Cheers Ryan Cliff Jansen (Interop Systems Inc) wrote > To add to Steve's comments: I took a look at what WCF related APIs are > missing in the "Compact" version of the Framework for Windows CE. > Most of it is there. Oddly, the missing bits appear to affect binary > encoding capability. This means that the binary and MTOM generic > bindings aren't available. Less obviously, it also means that the > interop case becomes problematic, which may or may not affect your > planned use. > > It should be possible to build the C++ based WCF channel minus the raw > encoder and associated binary binding. Since the full > XmlDictionaryReader/Writer functionality is missing, a different > strategy will be required for an alternate encoder. There will > probably be a small performance penalty, but it should be possible to > adapt the raw encoder's strategy to work within the Compact > Framework's XML capabilities. > > If you decide to go this route, give me a shout and I will help you to > the best of my abilities. > > Cliff > > ----- "Steve Huston" < > shuston@ > > wrote: > >> Hi Mike, >> >> > Thanks Steve for the answer and for your C++ port to windows >> >> You're welcome. >> >> > What do you think about the code port on WiinCE ? >> > do you think is better to do it in C++ ( based on the QPid >> > C++ Windows API client) >> >> This is the client I'm most familiar with and I believe it would be >> doable. >> >> > or in C# Dot Net Compact Framework[2.0 | 3.5] (based >> > on the QPid C# Dot Net s API client ) ? >> >> I'm not familiar with the dot net client that's been around for a >> while. I'm a bit more familiar with the WCF channel code that's just >> been included in the Qpid trunk (so will be in 0.6). If WCF is an >> option for you, you might consider this path as well. The WCF channel >> code relies on the C++ client you'd need to get both going. >> >> > What do you suggest or recommend to do ? >> >> Give it a try - it won't take long to build it and test it out a bit. >> >> -Steve >> >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto: > users-subscribe@.apache > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto: > users-subscribe@.apache -- View this message in context: http://qpid.2158936.n2.nabble.com/AMQP-QPid-client-API-for-WinCE-tp3604882p7601535.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org