Re: Re: Request for vote: HTTP_Status
| From: | Wolfram Kriesing | Date: | Sat, 30 Aug 2003 12:20:51 +0000 |
| Subject: | Re: Re: Request for vote: HTTP_Status | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-20880@lists.php.net to get a copy of this message | ||
yep, i think this could be an extension to HTTP_Header, my +1 for putting it there
just go ahead, once you have reached a common sense on the way to do it
/me back from vacations :-)
Martin Jansen wrote:
On Sat Aug 30, 2003 at 04:4209AM -0400, Marshall Roch wrote:-- Wolfram http://opensource.visionp.de ... authentication system .... http://sf.net/projects/authOk, I don't disagree with you, but I don't see any one package that it fits well in. I'd say HTTP_Header because of the name, but that package is currently designed to "set/modify HTTP-Headers." If we expand it to process headers as well, then it might be a good solution.I don't see a problem in extending it's purpose. Did you already try to contact Wolfram?Merging them the way it stands now would mean including all of HTTP_Header without gaining any benefit from it.Just to avoid confusion: You don't need to add your code to the main HTTP_Header class, but make it an independent file, just like Header/Cache.php.