Miguel de Icaza
03 Jan 2003 19:57:59 -0500
> I think it is, but the problem is with the semantics.
> System.Messaging is very tied to MSMQ, you can't even opt for another
> provider, like you do in ADO.NET and on J2EE JMS. That's why I started a
> Server Project.
> However, I want to extend System.Messaging (in truth, the extensions are
> planned to go within a Mono.Messaging namespace) to allow for pluggable
> queueing services providers, but it may penalize performance, or bypass
> server features: for instance, IBM's now renamed WebSphere MQ, have
> encoding/codepage conversion of messages built-in.
I do not have a lot of knowledge about how messaging works (more than
what I read from my COM+ book), but it looked relatively simple to
implement. Up to the point, that we wanted to implement it for Bonobo
back in the pre-Mono days.
It would be very fun to write such a beast in C#, but my knowledge is
Rusty, and I have promised myself not to write new code until I fix the
known bugs in my current code ;-)