An AppDomain can
be thought of as a lightweight process. Multiple AppDomains can exist inside a
Win32 process. The primary purpose of the AppDomain is to isolate applications
from each other, and so it is particularly useful in hosting scenarios such as
ASP.NET. An AppDomain can be destroyed by the host without affecting other
AppDomains in the process.
Win32 processes
provide isolation by having distinct memory address spaces. This is effective,
but expensive. The .NET runtime enforces AppDomain isolation by keeping control
over the use of memory - all memory in the AppDomain is managed by the .NET
runtime, so the runtime can ensure that AppDomains do not access each other’s
memory.
One non-obvious
use of AppDomains is for unloading types. Currently the only way to unload a
.NET type is to destroy the AppDomain it is loaded into. This is particularly
useful if you create and destroy types on-the-fly via reflection.
Yes, .NET
framework does support one-way messages. To set a void method as one-way
operation, set the OneWay property to true on SoapDocumentMethodAttribute or on
SoapRpcMethodAttribute attribute. In such cases, the Web service client is
intending to just send some notification to the server and not expect any
response. The server in such cases returns 202 Accepted HTTP response to the
client. And there will be no output message in the WSDL file for such methods.
The support for one-way Web service operations was also added in the latest
SOAP Toolkit 3.0 release.
Yes, in addition
to XDR and XSD schema validation, .NET continues to support the DTD to validate
the XML documents. The System.Xml namespace contains a class named
XmlValidatingReader that can be used to validate the XML documents.
It is a Text File
that contains the combination of the following:
• Text
• HTML tags
• Script Commands
• Text
• HTML tags
• Script Commands
One of ASP.NET’s
most useful features is the extensibility of the HTTP pipeline, the path that
data takes between client and server. You can use them to extend your ASP.NET
applications by adding pre- and post-processing to each HTTP request coming
into your application. For example, if you wanted custom authentication
facilities for your application, the best technique would be to intercept the
request when it comes in and process the request in a custom HTTP module.
Read All Questions :-asp.net interview questions part-(1 to 8)
You have gain more knowledge
Visit Daily
best of luck !
No comments:
Post a Comment