I think there's an MSMQ remotting sink available either fom MS or GotdotNew I think on of our projects used it without any problems.
-----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Brad Wilson Sent: Sunday, March 06, 2005 11:19 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] MSMQ or .net remoting The choice comes down to coupling. Communication via a messaging system like MSMQ de-couples the client(s) and server(s). You send your message off into the ether, and something sooner or later will come and get it and do someting with it. There's no direct connection, so clients and servers can send messages whether or not the recipient is alive. With remoting, you have an immediate and direct connection between a client and a server. The communication happens immediately, and feedback can happen immediately. The interaction model is quite a bit simpler, especially in the feedback case. However, the client and server must both be running and have some network connection to one another in order to communicate. FWIW, I think MSMQ is probably one of the most under-utilized pieces of software available to developers. It's flexible, high performance, and fairly easy to use from .NET. - Brad On Wed, 1 Jan 2003 10:11:29 -0200, Bruno N <[EMAIL PROTECTED]> wrote: > Im writing a distributed application, and i cant figure out wheter should i use .net remoting or msmsq to handle the communication between the componets in destributed computers. -- Brad Wilson http://www.dotnetdevs.com/ http://dotnetguy.techieswithcats.com/ "Customers don't want a drill. They want a hole." =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
