| A1:
|
True. A process may contain multiple AppDomains. True. An AppDomain may contain multiple assemblies. True. An AppDomain may contain .dll and .exe files. True. An AppDomain can be unloaded from a process.
|
| A2:
| Three activation modes: client activation, server activation (single call), and server activation (singleton). HTTP or TCP can be used with all. |
| A3:
| Single call server activation creates a new object on each call; single call singleton creates an object on the first call only. The object is then used for other calls. |
| A4:
| CurrentLeaseTime桝mount of time until object is available for Garbage Collection.
InitialLeaseTime桰nitial lifetime of a lease.
RenewalOnCallTime桝mount that CurrentLeaseTime is increased on called object. |
| A5:
| Set the LeaseManagerPoolTime in a configuration file to specify how frequently the lease manager checks for expirations. |
| A6:
| Client-activated and server-activated singleton use leases. |
| A7:
| c. A server-activated singleton object is created when the first call is made to the host object. |
| A8:
| Channel registration indicates the type of protocol to be used梪sually TCP or HTTP梚n the remoting and the port number to be used. Type registration specifies the available remote object and the activation mode type. |
| A9:
| An interface or SoapSuds is used to prevent having to place a full assembly on the remoting client's machine. The assembly provides metadata, but can also expose proprietary code. An interface provides only the metadata a client requires. SoapSuds extracts the metadata and places it in a file that is deployed on the client's machine. |
