
Originally Posted by
Mike-XS
@Nathan. I have a little suggestion. Would it be possible to draw up some kind of basic proxy optimisation / setup guide specific to the O2proxy servers to help proxy operators keep the server running smoother. I don't know if you could enforce it, but some kind of setup/optimisation guide could give people a starting point for getting their proxy setup in the most compatible way for O2proxy servers..
I'd certainly consider adjusting my proxy settings if it would help keep the server up, hopefully others would adopt it too if it means less downtime. Would that help at all , or not worth the trouble ?
Thats sort of what I was leaning towards saying. It would be a good to have everybody unformally running the same script, I would choose Glype, with it all ompitizmed. Remove Disk I/O by turning Apache logs off, caching off being mandatory, and have all them uniformally writing to the same Custom Glype log file making abuse issues easier, since your have just one log file with unencrypted urls all listed by date.
There is also many function and systems calls in the glype script that can be removed too. For example in the index.php this,
PHP Code:
/*****************************************************************
* Check PHP version
******************************************************************/
if ( version_compare(PHP_VERSION, 5) < 0 ) {
$themeReplace['error'] = '<div id="error">You need PHP 5 to run this script. You are currently running ' . PHP_VERSION . '</div>';
}
That is a useless system call on each view of index.php and could just be deleted.
Bookmarks