[openamq-dev] Managed .NET client implementation?

[Karl Waclawek]

Although it is possible to wrap the WireAPI with a .NET interface, this 
is not the most desirable approach, because "unsafe" code cannot be 
executed everywhere. So, the ideal solution would be an OpenAMQ client. 
written completely in .NET. Are there any plans in this direction?

If there are, the second question is, which API to expose. There does 
not seem a long-standing tradition for a message queue API in the .NET 
world, so a direct translation of the WireAPI would be OK. However, the 
new WCF framework includes support for message-queueing, so one should 
probably also look into how the WireAPI could be plugged in.

Just curious,

Karl