> Interesting. I would have for sure put it at being slower - > unless there is a cracking network in place.
Well, that's what I thought too, but I guess the cost of running both processes on the same server can outweight the cost of having the servers communicate across a network. You run into the same issues with running separate database and web application servers, and we recognize the advantage of doing that. > This setup however, can and in most cases produces a single > point of failure with a single code repository. How is there any more a single point of failure than there would be if you put both servers on the same machine? Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:10:5926 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/10 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.10 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
