RE: [PHP4BETA] RE: JSP vs. PHP - Two vs. Three Teir

The logical separation is dictated by the classes we define in PHP. I may have one class that will iterate product choices into a list and another class that creates a dropdown list in HTML. I pass the results of one to the other and away we go. -----Original Message----- From: Michael Nino [mailto:mnino@Insight.com] Sent: Friday, April 07, 2000 3:13 PM To: 'Dan'; php4beta@lists.php.net Subject: RE: [PHP4BETA] RE: JSP vs. PHP - Two vs. Three Teir Thank you for you opinion. more.com endorse a similar approach. How do you logically implement the business logic-- programatically speaking? One approach that I'm investigation is a PHP service by setting the timeout to zero thereby providing persistenct services to other executing PHP scripts? Do you know of this implementation? Would you be interested in speaking in person? thanks!michael -----Original Message----- From: Dan [mailto:dan@savage-comedy.com] Sent: Friday, April 07, 2000 4:08 AM To: php4beta@lists.php.net Subject: [PHP4BETA] RE: JSP vs. PHP - Two vs. Three Teir We started off using a classic three tier system - linux/Apache/PHP web server, linux/C++ daemon transaction server and Sun/Solaris/Oracle database. We found that when our site got busy (200+ users per webserver), the overhead of passing data to/from the transaction server was considerable. We went to two CPUs per webserver and placed all of the logic for the transaction server into PHP that ran on the webserver. We can now scale by adding new webservers, the first candidates being the old transaction servers. I think of this approach as a "logical" 3 tier approach. I really like doing everything in PHP, it's fast to develop on, it runs quickly and reliably (we're still using beta2 of version 4!) and in the end, our bottleneck is our database. I don't think the stuff they push in books has a whole lot to do w/real world web traffic. <sound of two pennies hitting table>