Re: [PHP4BETA] additional headers in include and require functions

| FN>> And an empty register_http_header() unregisters the hash | FN>> from being automatically added to all requests (yes it makes | FN>> sense, or perhaps unregister_http_header(), buy why pollute | FN>> the namespace?) | | This seems to be exactly the same as, for example, adding parameter to | include/open/whatever, only with long-time effect. But we do not really | want to register any HTTP headers, we want to open file via with those | headers. So why don't we say what we want? Why we need two function calls | each time (you *have* to unregister them, or you forget them and your next | HTTP-ized fopen will pass your headers to some alien site)? Won't it be | easier just to do what we want to be done? | You mean directly connect through fsockopen() and do the stuff ourselves? Or perhaps you are suggesting an option for headers in fopen? fopen ( filename , access , "Referer: http://blah.com/etc\nMore: etc" ); But the third parameter is already refered for use include path? Either is fine with me. But I thought ease was the main concern of PHP. And when you do programming, forgetting something will always have effect on the outcome, be it a simple character in a variable name or unregistering a hash for fopen()/include() etc. Enjoy! Faisal