[WebMethod]using System.Web;using System.Web.Services;

System.Reflection

The part of a URL passed by an HTTP request to invoke a servlet. A URL path consists of the context path + servlet path + path info, where Context path is the path prefix associated with a servlet context of which the servlet is a part. If this context is the default context rooted at the base of the Web server's URL namespace, the path prefix will be an empty string. Otherwise, the path prefix starts with a / character but does not end with a / character.

Servlet path is the path section that directly corresponds to the mapping that activated this request. This path starts with a / character.

A standard that lets you specify a unique label for the set of element names defined by a DTD. A document using that DTD can be included in any other document without having a conflict between element names. The elements defined in your DTD are then uniquely identified so that, for example, the parser can tell when an element should be interpreted according to your DTD rather than using the definition for an element in a different DTD.

A preconfigured JMS object (a resource manager connection factory or a destination) created by an administrator for the use of JMS clients and placed in a JNDI namespace.

An API for processing XML documents. JAXP leverages the parser standards SAX and DOM so that you can choose to parse your data as a stream of events or to build a tree-structured representation of it. JAXP supports the XSLT standard, giving you control over the presentation of the data and enabling you to convert the data to other XML documents or to other formats, such as HTML. JAXP provides namespace support, allowing you to work with schema that might otherwise have naming conflicts.

An API for processing XML documents. JAXP leverages the parser standards SAX and DOM so that you can choose to parse your data as a stream of events or to build a tree-structured representation of it. JAXP supports the XSLT standard, giving you control over the presentation of the data and enabling you to convert the data to other XML documents or to other formats, such as HTML. JAXP provides namespace support, allowing you to work with schema that might otherwise have naming conflicts.

Web forms are very similar to traditional HTML forms. The difference is that Web forms are server-based, meaning you create the user elements on the server. The server has complete knowledge of what the interface looks like, what it can do what data it expects, and so on. Web forms pages are divided into two parts: the visual elements and the accompanying UI logic. These two components are completely separate from each other conceptually, and they can be physically located anywhere you want. Typically, both parts are contained within one .aspx file. The System.Web.UI namescape defines classes and interfaces used in constructing nd rendering elements on a Web form. The most important class in the System.Web.UI is the Control class which defines the properties, methods and events that are common in all server controls in the WebForm framework. Another important class in this namespace is Page which is a derivative of the Control Class. All ASP.NET web pages are instances of derivatives of the Page Class. To have an extensible framework, the System.Web.UI namespace also includes the UserControl class which is similar to Page class except that it is mainly used as the base class for user controls.

Directives are used to pass optional settings to the ASP.NET pages and compilers. They typically have the following syntax: <%@ directive attribute=value [attribute=value] %> Directives are typically located at the top of the appropriate file, although that is not a strict requirement. For example, Application directives are at the top of the global.asax file, and Page directives are at the top of the .aspx files. Application directive: The Application directive is used to define application-specific attributes. It is typically the first line in the global.asax file. Assembly directive: The Assembly directive links an assembly to the application or page at parse-time. The Assembly directive is contained in either the global.asax file, for application-wide linking, or in a page (.aspx) or user control (.ascx) file, for linking to a specific page or user control. There can be multiple Assembly directives in any file. Each Assembly directive can have multiple attribute/value pairs. Control directive: The Control directive is used only with user controls and is contained in user control files (.ascx). There can only be a single Control directive per .ascx file. Import directive: The Import directive imports a namespace into a page, user control, or application, making all the classes and namespaces of the imported namespace available. Page directive: The Page directive is used to define attributes for the page parser and compiler specific to the page (.aspx) file. There can be no more than one Page directive for each page file. Each Page directive can have multiple attributes.

Threads are lightweight programs responsible for multitasking within a single application. The System.Threading namespace provides classes to manage multithreaded applications. The simplest way to create a thread is to create a new instance of the Thread class. CLR provides ThreadStart delegate which points to a method which starts when the thread starts running. Thread myThread = new Thread (new ThreadStart(myfunc)); There are API's to join threads, suspend threads and killing threads as well.