Processing requests
In a standard Web Connection part like the To-do List example in the previous chapters, incoming requests are processed automatically. Each request causes the part to process the incoming form data (if any) and generate HTML to be sent back to the client browser.
However, not all application designs can be satisfied with this default behavior. The Web Connection feature provides several nonvisual parts that you can use to handle incoming requests in ways other than the default. The ways you might use these parts include:
•Using incoming requests to trigger processing that takes place with each request
•Conditionally routing requests to different pages
•Accessing the variables passed from the client
•Accessing data from forms not built with Web Connection
Last modified date: 01/29/2015