Dcom replacement is Remoting.
Use remoting for more efficient exchange of information when you control both ends of the application.
Remoting is designed to .Net to .Net Communication.
Remoting object calls different Application Domains.Remote objects runs in different process client calling the remote object can't call it directly. so they uses proxy.
Namespace::: System.MarshllbyRefObject.
Remoting depends on
1) Channels
tcp(transaction commit protocol) data representation.
http(hypertext transperprotocol) xmlbased syntax
2) Serialization & DeSerailization
Coverting object into stream Serialization
Reading the stream and constuction object is Deserialization.
3)Formatter classes
Binaryformatter::: it is used by tcp channel
Soap formatter:::: it is used by http channel
NameSpace:::: System.Runtime.Serialization.Formatters.Binay/soap
Serialize(object,stream)
DeSerialize(Stream)
4)Activation modes
client activated and serveractivated.
Serveractivated:: when user makes a call to the method of class, the object creation takes place.
client activated:: whenever the client request comes to the remote server an object will be created and the reference will be send to client application.
Client activated objects maintain state.
Marshal byvalue:: when the client request comes, object will be created on the server machine. This object will be send to client machine.
Marshl byReferece:: when the client request comes, object will be created on the server machine. This object reference will be send to client machine.
Singlecall:: When user makes a call to the method, the object will be created, after sending the response the object will be destroy.This is stateless.
For single cleint we have single object.
SingleTon:: This will maintain single object for all the clients at a time. The lifetime will be 5 min by default.
client can be created objects on the server by two ways, one is using Keyword "NEW" and seconde one is "Activator.CreateInstace().
Try AuctionAds
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment