Why not just connect the 2 servers together with additional nic cards, then the second is only accessable from the first.
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. > -- Cheers Mike Morton **************************************************** * * Tel: 905-465-1263 * Email: [EMAIL PROTECTED] * **************************************************** "Indeed, it would not be an exaggeration to describe the history of the computer industry for the past decade as a massive effort to keep up with Apple." - Byte Magazine Given infinite time, 100 monkeys could type out the complete works of Shakespeare. Win 98 source code? Eight monkeys, five minutes. -- NullGrey -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
