cvs: php-src(PHP_5_2) / README.input_filter

rasmus Mon Oct 30 17:11:02 2006 UTC Modified files: (Branch: PHP_5_2) /php-src README.input_filter Log: Pierre requested an update to this. I don't think it makes sense to remove what little API docs we have here, and the simple example in this doc is a lot easier to follow than ext/filter. http://cvs.php.net/viewvc.cgi/php-src/README.input_filter?r1=1.7.4.1&r2=1.7.4.1.2.1&diff_format=u Index: php-src/README.input_filter diff -u php-src/README.input_filter:1.7.4.1 php-src/README.input_filter:1.7.4.1.2.1 --- php-src/README.input_filter:1.7.4.1 Tue Dec 6 02:30:18 2005 +++ php-src/README.input_filter Mon Oct 30 17:11:02 2006 @@ -10,7 +10,10 @@ through which a company-wide or site-wide security policy can be enforced. It is implemented as a SAPI hook and is called from the treat_data and post handler functions. To implement your own security -policy you will need to write a standard PHP extension. +policy you will need to write a standard PHP extension. There is also +a powerful standard implementation in ext/filter that should suit most +peoples' needs. However, if you want to implement your own security +policy, read on. A simple implementation might look like the following. This stores the original raw user data and adds a my_get_raw() function while the normal @@ -85,7 +88,7 @@ { php_info_print_table_start(); php_info_print_table_row( 2, "My Input Filter Support", "enabled" ); - php_info_print_table_row( 2, "Revision", "$Revision: 1.7.4.1 $"); + php_info_print_table_row( 2, "Revision", "$Revision: 1.7.4.1.2.1 $"); php_info_print_table_end(); }