Re: Package proposal: HTTP_Status
| From: | Stefan Neufeind | Date: | Tue, 26 Aug 2003 09:39:50 +0000 |
| Subject: | Re: Package proposal: HTTP_Status | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-20524@lists.php.net to get a copy of this message | ||
On 26 Aug 2003 at 15:08, Alan Knowles wrote:
> Marshall Roch wrote:
> > Alan Knowles wrote:
> >
> >> I'd suggest someone does a status_codes.ini file and both (all?)
> >> packages share it..
> >
> >
> > Sounds feasible, but HTTP_Status provides other methods that are
> > still useful. Also, I wonder if it's more work to parse an ini file
> > than to include a file. I've never worked with ini files like that,
> > so I have no idea.
>
> ini files are probably marginally faster than a php array.. as the
> parser is slightly simpler than the php parser...
>
> I've never benchmarked it however...
But you still need to read ini-files into arrays, right? Wouldn't
this cause more time to be consumed (e.g. if you use one of those ini-
file-reading-classes) than simply including a php-file? Since the
codes are not to be adjusted by a user and don't change regularly I
don't see why an ini-file would be needed.
Anybody has experience on the perfomance-questions? From my side a
php-file should be faster when included.
Stefan