> I trust that I am not the only one to be curious to
> learn more concerning your remark.
[...]
> Would you care to explain in more details why PHP is
> a MUST DON'T to do this?
Hi,
Thanx for your comment.
One can talk about things like load balance for scalability,
and other boring subjects, but I agree that it is of course
hard to establish what is meant with a "good" design without
knowing the purposes. But, my general view goes this:
"Of course you can use a hammer to nail a screw, but
a screw driver will do the job much easier and better."
ARGUMENT OF COUPLING & COHESION:
By using for instance PHP for parsing a large text files,
you are stealing resources from the web server (assuming
PHP runs as an instance within Apache), resources better
used elsewhere for other purposes.
A single application (the parser) can be executed in
its own processing space and given independent priority,
this will favoring parallelism with multi CPU system;
if the parser is smart enough written it might even
utilize several CPU's, possible running with low priority
as a background task.
If the system become over loaded, then parser
application can easily be moved onto another system.
Anyway, the main idea is that you wants to keep the
pears and apples separated from each other.
By the way; You're fired! :)
//Anders
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
