.NET Remoting Channels (Custom)
-
There are two types of channels that .NET framework provide 1)TCP and 2)HTTP and there are custom channels that u can create using any stream oriented transfer technology like Sockets, Named Pipes and MSMQ. My question is which channel is suitable in which situation. Can anybody tell me when should i use named pipes channel and when MSMQ. Need urgent response .... @!$h@
-
There are two types of channels that .NET framework provide 1)TCP and 2)HTTP and there are custom channels that u can create using any stream oriented transfer technology like Sockets, Named Pipes and MSMQ. My question is which channel is suitable in which situation. Can anybody tell me when should i use named pipes channel and when MSMQ. Need urgent response .... @!$h@
I'd say, use an HTTP channel when you want to traverse a firewall and a TCP channel when you're working entirely within a single site. If you need to work with a network that doesn't support TCP, you might use Sockets to create an IPX stream, for example. Or, you could use Named Pipes to support any stream protocol that Windows supports (and, in addition, get support for impersonation, though this might be tricky to handle). You might use MSMQ if you wanted to queue up requests to level out workload and provide failover capabilities. I'm not actually sure this would be possible with remoting. Stability. What an interesting concept. -- Chris Maunder