From the user perspective, we basically need a messaging solution, which is
a)robust b)have a nice dotnet client for Windows c)have a nice C++ client for
Linux.
I believe, this is the most common scenario imaginable. Everything else, like
Mono compliance or fanciness of WCF are somewhat secondary goals, though
possible and desired.
For the moment, as I can understand from reading this list, on Windows we can
only make use of either half-ready dotnet client or try C++ Interop. But the
most possible scenario is that we opt for RabbitMQ instead which seem to
provide all the basic connectivity that is really really needed.
Alexei,
If you have the a few cycles it would be great to also get your feedback
on the WCF client Cliff has been working on for the 0.6 release in
process. I also see that Adian (thanks) has been committing the patches
for 0-10 pure C# client so I think there will be two pretty good options
from the project in 0.6.
I.e. we would love to have you as a happy Qpid user, so let us know how
we can make you successful .... and maybe one day join the project if
you get sucked in :-)
The additional question for the qpid project is how we iterate these
forward, which we should start another thread on.
Carl.
