Microsoft .NET Remoting allows applications running in different application domains or processes to communicate. By default, remote components communicate either over transmission control protocol (TCP) or Hypertext Transfer Protocol (HTTP). One of the problems with cross-process communication is authentication. To take advantage of Windows authentication, you should use HTTP for remote communication. This allows you to host the remote component in IIS, which supports Windows authentication. If you use TCP for remote communication, you would need to implement a custom authentication mechanism.
0 comments:
Post a Comment