Thursday
Improving DataSet Serialization and Remoting Performance
Improving DataSet Serialization and Remoting Performance: "Improving DataSet Serialization and Remoting Performance"
.NET Remoting Architectural Assessment
.NET Remoting Architectural Assessment: ".NET Remoting Architectural Assessment"
Executive Summary
.NET Remoting is a useful tool to employ in certain types of distributed solutions. It offers an extensible model in terms of the protocols and message formats it can support and can offer performance advantages in specific scenarios. It should not be deployed directly on the Internet and its server objects should be hosted under IIS in order to benefit from the security and performance features that IIS provides to processes running under its control.
Remoting should be considered for "closed world" distributed solutions where both client and server are CLR-managed processes. Examples are as a component at any tier within an intranet solution either over a secure TCP channel such as IPSec or over HTTP or as a middle-tier application component conversing with a .NET Web tier component over a firewall; in this case, the HTTP channel with the binary formatter should be chosen after the solution has been proven using the SOAP formatter.
For systems that need to interoperate with non-CLR clients, use ASMX Web services, taking care to avoid some of the pitfalls with respect to datatypes (refer to the section on Strong Type Support).
Note that hosting outside of IIS using TCP brings with it performance benefits, but at the cost of requiring custom security.
Design and Implementation
Executive Summary
.NET Remoting is a useful tool to employ in certain types of distributed solutions. It offers an extensible model in terms of the protocols and message formats it can support and can offer performance advantages in specific scenarios. It should not be deployed directly on the Internet and its server objects should be hosted under IIS in order to benefit from the security and performance features that IIS provides to processes running under its control.
Remoting should be considered for "closed world" distributed solutions where both client and server are CLR-managed processes. Examples are as a component at any tier within an intranet solution either over a secure TCP channel such as IPSec or over HTTP or as a middle-tier application component conversing with a .NET Web tier component over a firewall; in this case, the HTTP channel with the binary formatter should be chosen after the solution has been proven using the SOAP formatter.
For systems that need to interoperate with non-CLR clients, use ASMX Web services, taking care to avoid some of the pitfalls with respect to datatypes (refer to the section on Strong Type Support).
Note that hosting outside of IIS using TCP brings with it performance benefits, but at the cost of requiring custom security.
Design and Implementation
Performance Comparison: .NET Remoting vs. ASP.NET Web Services
Performance Comparison: .NET Remoting vs. ASP.NET Web Services: "Performance Comparison: .NET Remoting vs. ASP.NET Web Services"
Tuesday
HttpWebRequest and the Expect: 100-continue Header Problem
HttpWebRequest and the Expect: 100-continue Header Problem: "HttpWebRequest and the Expect: 100-continue Header Problem"
Friday
Monday
Programming with Microsoft Transaction Server and an Oracle Database Server
Programming with Microsoft Transaction Server and an Oracle Database Server: "return OCI service and environment handles to client "
Wednesday
Friday
Brock Allen's Blog
How to do custom handlers for IIS 6.0? This was presented in my Guerrilla.NET class
Subscribe to:
Posts (Atom)
