Quote:
Originally Posted by speed
My question is simple, why would you want to do this?
|
And so is my answer. How large do you think your content document will be once the API, is in place to be included centrally in php.ini / .htaccess or like this:
PHP Code:
<?php include $_SERVER['DOCUMENT_ROOT'] . '/include/myAPI.class.php' ;
How difficult is it to change that API site wide? Did you look at the source of my examples regarding my main domain and the add on domains above? You can of course not see the PHP code, but you may guess some of the functionality.
You can also see the content of
robots.txt but not of .htaccess. The semantic content and code / markup that the Bots see is stripped to a minimum. SEO effect? Saving bandwidth? Saving storage? In essense, your site content, aside from the API is reduced to a long content string (at least for text content).
Finally:
Why should you need to validate your markup? Can that not be done on the highest level with:
Throw, try and catch exeption handling?
If your API si well written, you should not even need to validate. You get a message like this:
- Fatal error, this input is not allowed.
- Error this input is not reccomended.
- Warning this input is well-formed, but not valid.
Using AJAX functionality, you may not even need to reload the page. You can only change the input line where the error is.