On Sun, 22 Sep 2002 11:31:17 -0500, you wrote: >Basically, it's really easy to create multiple interfaces to the same >business logic. Don't try to make things more complicated than >necessary, and since there is no need to use multiple languages in your >implementation, that is a complexity worth avoiding.
Point well taken. However, allow me to explain some things that I left out of my original post: I decided to go with Perl for a few different reasons. First of all, I wanted to get more comfortable working with Perl, mainly so I could get exposed to languages other than PHP. I had used Perl in the past, but only for small tasks. I saw this project as an opportunity to pick up some useful Perl experience. Another reason I went with Perl is because IMHO some of the tasks I needed to accomplish are just easier done in Perl. Part of the functionality of my script is to parse incoming email and take different actions based on it's content. My script responds to certain embedded commands (subscription confirmations, unsubscribe requests, requests for automated help, etc.). It also forwards unknown commands to one set of addresses, while forwarding DSN's to another set. This means accepting the mail on STDIN and doing a lot of regex parsing. I know that this is more than possible in PHP, but Perl just seems better suited to this type of task IMHO. In retrospect it probably would have been better for me to implement everything in PHP, from a modularization point of view. I could have, like you suggested, put all of my business logic in say a class, and included that class from both my webpage and my mail script. But that would lock me in to using PHP for everything that needed access to that business logic, so I'm still not sure that is the best solution... Thanks for the response... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
