Showing posts with label CAO. Show all posts
Showing posts with label CAO. Show all posts
Wednesday, 25 January 2012
In CAO model for client objects to be created by “NEW” keyword what should we do?
Remoting Clients and Remoting Server can communicate because they share a common contract by implementing Shared Interface or Base Class (As seen in previous examples). But according to OOP’s concept we can not create a object of interface or Base Classes (Abstract Class). Shipping the server object to client is not a good design practice. In CAO model we can use SOAPSUDS utility to generate Metadata DLL from server which can be shipped to client, clients can then use this DLL for creating object on server. Run the
Saturday, 14 January 2012
What is an application domain ?
Previously “PROCESS” where used as security boundaries. One process has its own virtual memory and does not over lap the other process virtual memory; due to this one process can not crash the other process. So any problem or error in one process does not affect the other process. In .NET they went one step ahead introducing application domains. In application domains multiple applications can run in same process with out influencing each other. If one of the application domains throws error it does not affect the other application domains. To invoke method in a object running in different application domain .NET remoting is used.
.NET remoting is replacement of DCOM. Using .NET remoting you can make remote object
One process can have multiple Application domains
What is .NET Remoting ?
.NET remoting is replacement of DCOM. Using .NET remoting you can make remote object
Subscribe to:
Posts (Atom)