[Mono-list] Reply: How about System.Messaging?
A Rafael D Teixeira
Tue, 28 May 2002 16:38:22 -0300
>From: "Stijn \"Adhemar\" Vandamme" <firstname.lastname@example.org>
>>At the moment the messaging guys seem to be quite happy with their
>>proprietary protocols, enjoying the benefits of locking people into
>How about Jabber?
>Or am I missing the point and is that something completely different?
"The System.Messaging namespace provides classes that allow you to connect
to, monitor, and administer message queues on the network and send, receive,
or peek messages."
In short, MSMQ. It´s not something like jabber (instant messaging), it´s
asynchronous messaging through queues.
I think of implementing some daemon for doing it on Linux, and integrate
into Mono (surely I´ll write the daemon in C#/Mono).
But the real problem is that USEFULL queues do more than serialize messages,
they are also translators (have you ever tried to send an XML file in UTF-8
to a mainframe?). And, specially, they are platform bridges, making the very
different latency/rate specs of big-iron and microcomputers somewhat marry
(mainframes make you wait until they can process your request, and then send
bytes blazing over your head, microcomputers normally does the reverse, they
can serve almost in not time, but can accept/send some measly megabytes a
The first item, can be addressed migrating IBM-enhanced xerces zillion-
encodings support, from java to mono. We´ll do it, ASAP.
The second is hard just because, as someone said, wire protocols to speak
(connect) with queues in mainframes and clustered servers are proprietary.
For now, we´ll be an island, but perhaps our open messaging server will
prove itself successfull, and market will migrate to it, bringing in some
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.