Web 1.WebClass Introduction:
WebClass is a VB component that resides on the Web SERVER and responds to browser input.
For users, an IIS application seems to consist of a series of HTML pages. For developers,
An IIS application is made up of some special types of objects called WebClass.
2. IIS Applications and ASP applications
The IIS application is superficially similar to the Active Server Pages application. Both applications display dynamic WEB sites and perform their processing on the server rather than on the client. However, each has its own unique advantages.
Active Server pages is suitable for scripting developers interested in making Web pages, and it provides the unique ability to mix scripts and HTML.
IIS applications are suitable for constructing Visual Basic developers based on Web applications rather than web pages. IIS applications allow complex transactions, and almost any browser or platform can easily access it.
3. Advantages of IIS Applications:
A familiar development environment and model. You can use Visual Basic knowledge to add classes (Class), modules (model), or any Visual Basic ActiveX parts to your project, and are therefore easy to debug and write.
The breadth of the use of $. can be supported by most browsers.
$ reusable parts. Similar to OOP programming. Each object can be accessed between each other.
The $ code is separate from HTML: Unlike writing an ASP application. Separation of Server-side handlers and client-side programs. Easy to maintain and modify.
$. Customizable handling events, thus writing methods flexibly
4. IIS Application Disadvantages:
The "Get" method in all template files cannot be connected to events in WebClass, so you must use the "Post" Method ...
. WebClass sometimes you may get an error when you format a template file to send to the browser.
5. asp file and WebClass relationship
An ASP object that a WebClass can use includes:
? The request-accepts the request from the browser's end user.
? Response-sends information to the browser to display it to the user.
? session-maintains information about the current user session and saves and obtains status information.
? application-the administrative state shared by multiple WebClass instances.
? server-create additional objects and determine server-specific properties that may affect WebClass processing.
The composition of the 6.Webclass.
WebClass consists of HTML templates and custom WebItem. (HTML templates and custom WebItem collectively WebItem), of course, not necessarily include templates and custom WebItem.
$. An HTML template file is an HTML page associated with WebClass. When WebClass receives a request, it can send the HTML page for display to the browser. The difference between a template and a regular HTML page is that it often contains a replacement area that WebClass can handle (usually a range defined with the "wc@" label) before it is sent to the browser. This allows you to customize your own responses.
$. A custom WebItem is a program resource consisting of one or more event handlers. These event handlers are invoked by the browser when the page loads or when the user selects an HTML element. These event handlers can produce a response to the browser or pass the processing to another WebClass WebItem.
You can have multiple WebClass (that is, there are multiple corresponding ASP files.) Each ASP file control (host) is a WebClass.
Data interchange between $1.webclass can be passed through session variables, application variables, or directly from a WebClass to call processing events in another WebClass---------WebItem. (Invoke method: ... action= "called WebClass name. asp? Wci=webitem&wce=wcevent&wcu=urldata "or other method).
$. There are two ways to convert between WebClass. Redirect "and" Set nextitem= ' WebItem '
? Note: In EndRequest, ProcessTag, the FatalErrorResponse event ignores the Nextitem attribute.
