Difference between revisions of "Ns register adp"
Jump to navigation
Jump to search
m |
|||
| Line 1: | Line 1: | ||
| − | Similar to Registered Procedures, all requests to a particular URL can be captured but in this situation processing can be performed by an ADP file. Giving additional functionality of being able to make changes a lot more rapidly. | + | Similar to Registered Procedures, all requests to a particular URL |
| + | can be captured but in this situation processing can be performed | ||
| + | by an ADP file. Giving additional functionality of being able to make | ||
| + | changes a lot more rapidly. | ||
| − | This also provides a method of making view controls at ADP level rather than at TCL level, which keeps development at an appropriate abstracted level. | + | This also provides a method of making view controls at ADP level |
| + | rather than at TCL level, which keeps development at an | ||
| + | appropriate abstracted level. | ||
Syntax: | Syntax: | ||
| Line 7: | Line 12: | ||
ns_register_adp GET|POST /URL/* FILE | ns_register_adp GET|POST /URL/* FILE | ||
| − | Both registered ADP pages, and registered procedures will be called irregardless of to original requested target existing or not. | + | Both registered ADP pages, and registered procedures will be called |
| + | irregardless of to original requested target existing or not. | ||
Revision as of 06:48, 14 November 2005
Similar to Registered Procedures, all requests to a particular URL can be captured but in this situation processing can be performed by an ADP file. Giving additional functionality of being able to make changes a lot more rapidly.
This also provides a method of making view controls at ADP level rather than at TCL level, which keeps development at an appropriate abstracted level.
Syntax:
ns_register_adp GET|POST /URL/* FILE
Both registered ADP pages, and registered procedures will be called irregardless of to original requested target existing or not.
