Re: Mail/mimeDecode.php
| From: | (Marc Logemann) | Date: | Tue, 04 Sep 2001 19:31:08 +0000 |
| Subject: | Re: Mail/mimeDecode.php | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1784@lists.php.net to get a copy of this message | ||
>> But the problem is, that this is also an extension.
>
>This is a dangerous line of thinking. I don't think it's very healthy to
>go around re-implementing everything that sophisticated c libraries do
>in php user- space - it's a lot of duplicated effort, it's _slow_ ...
>
>-chuck
You are right on this one, but let me explain some issues that will
prove thats not totally weird to do something like this:
Suppose you want to create a software package which should run
on each major hosting companies servers. Assume you code a groupware :)
Of course you will need MIME parsing functions, because you will
have some kind of webmailer. BUT this application (webmail) is
only 2 percent of the whole project. Now you must force users/hosters
to implement something like --with-imap or --with-mimedecode
(dont know the exact name) only to have a functional webmailer?
i dont like the idea that some big percentage of users wont use
our software, just because they are too dumb or too whatever to
intergrate certain modules into php (big hosting companies mostly
dont care about such stuff).
You are right with:
its slow
its double work
But this wont kill my arguments... (BTW i know how slow such
parsing Class is, i wrote one, but better slow than nothing)
You can allways say later on: Yeah its slow, if you want speed
get a better server (a better PHP installation).
--
Marc Logemann (aka Loge, www.marc-logemann.de)