[openamq-dev] Managed .NET client implementation?

[Karl Waclawek]

Pieter Hintjens wrote:
> Karl,
>
>   
>> So, the ideal solution would be an OpenAMQ client.
>> written completely in .NET. Are there any plans in this direction?
>>     
>
> It just takes one .NET expert and a week or two... :-)  We'd love to
> make this.  Do you know anyone who has .NET networking expertise?
>   

Not personally. The guys over at http://zeroc.com have ported their 
middleware to C#, so maybe you could ask them if they know anyone.

The only thing I would be good at is .NET interop (I have done Berkeley 
DB). So I could wrap the WireAPI dll in .NET, but that is not so 
desirable - therefore my post o this list.
> Probably, the WireAPI is the essential API because it gives full
> control over the protocol.  But this can be layered with other APIs
> that conform better to the language standards.  We have the same issue
> in Java, with JMS.  Most existing messaging expects JMS, but to really
> get the most from AMQP you need something like WireAPI.
>
> What we expect is that in a few years people will all adopt something
> like WireAPI for direct messaging work because it's simple and it
> works the same in all languages.  And on top of WireAPI we can make
> all kinds of frameworks (e.g. APIs that deliver messages of specific
> formats to applications).
>
>   

To change the subject a bit: Do you know of any paper that discusses in 
which scenarios it is better to use messaging (if sufficiently fast) 
where one would have traditionally used RPC-style (ICE, DCOM, CORBA, 
SOAP) interaction?

Karl