On 06/26/2003 07:43 PM, Mike Morton wrote:
Why not just connect the 2 servers together with additional nic cards, then the second is only accessable from the first.
That is the point but if you make the database server accessible from the Web server, anybody that hacks the Web server, can hack the information in the database server, making having the two servers pointless.
On 6/26/03 6:26 PM, "Manuel Lemos" <[EMAIL PROTECTED]> wrote:
Hello,
On 06/26/2003 02:10 AM, Joseph Szobody wrote:
A safer architechture would be to use two machines. One to act as the Web server and the other to process transactions. The Web server would take the orders and request the transaction server to process them.
The transcation server can only be accessed from the Web server. Nobody should be able to reach the transaction server from the Internet. The transaction server machine should have the database server too. The database server should not accept network connections.
Having never setup a multi-server web environment before, I'm a bit curious. How would the public server communicate with the private server, passing in database queries and getting results, if it can't connect directly to the database? Are we talking about building a SOAP interface between the two?
Yes, it could be SOAP although a less bloated protocol over HTTP would do.
--
Regards, Manuel Lemos
Free ready to use OOP components written in PHP http://www.phpclasses.org/
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
