Skip to main content

Request Processing

A typical CSP application generates dynamic Web pages in response to client requests. These Web pages contain a mixture of data, HTML, and JavaScript. Here is the sequence of events that occur after a client, most likely a Web browser, requests a CSP page from a CSP application:

  1. The Web Server receives the request, specifically an HTTP Request, for a page. Then, depending on its configuration, the Web server may forward some of these requests to the CSP gateway. It might forward requests for files with .csp or .cls extensions, for example.

  2. The CSP Gateway, then, depending on its configuration, can re-package the request and forward it to the correct CSP server.

  3. The CSP server decodes the request and determines the CSP application and class that has been requested — MyPage.cls. The server creates an instance of the class and then invokes its onPage method.

  4. The CSP server bundles the output of the onPage method into an HTTP Response.

  5. The CSP server sends the HTTP response to the CSP Gateway, which sends it to the Web Server, which in turn sends it back to the client that sent the initial request.

generated description: sequence1

FeedbackOpens in a new tab