Re: Mail/mimeDecode.php
| From: | (Marc Logemann) | Date: | Tue, 04 Sep 2001 19:45:17 +0000 |
| Subject: | Re: Mail/mimeDecode.php | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1794@lists.php.net to get a copy of this message | ||
Hi,
>I don't like userland implementations if there are
>already existing extensions, but I have one suggestion:
>the corresponding userland implementation *MUST* give
>advice that there exists already an extension which does
>the same thing (and perhaps better) and that user should
>use the extension if it's possible for him. If not, he
>should use the userland implementation instead.
This is what Richard wrote some minutes ago, by having
the same interfaces in the userland impl. the user
get "fast and native" parsing if he has the extension,
otherwise he will get a "not fast but also ok"
userland implementation. You could test this
during runtime and the user has no problems...
>With this statement you can avoid that people think
>"Oh, PHP can't parse mails natively" etc.
the normal guy probably wont even recognice if its
an extension or not, he only does if there
is a 5 megabyte email waiting to be parsed :))
(to keep the example of the mime decoding class)
--
Marc Logemann (aka Loge, www.marc-logemann.de)