This (and many other posts like it) seem to assume an architecture in which the web tier and app server tier are on separate machines It has been suggested to me to use an architecture with those two logical tiers on the same physical machines with a HA database system running on another set of machines. Is there any reason to avoid that architecture? Surely the emphasis on network chatter would be between the app server and the database server. -----Original Message----- From: Dan Hinojosa [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 13, 2000 10:34 AM To: [EMAIL PROTECTED] Subject: Re: Reason for using entity bean Network/Internet traffic is one reason. From the client to the session bean is one thread. That one client is calling on multiple entity beans. But since they are on the same server the data gets accessed via the speed of the hardware (which is pretty fast). Your session bean does your work on the server and returns the results, rather than the client having references to all the entity beans and performing the logic on your machine. -- Dan Hinojosa Java & Lotus Notes Consultant Java Certified Programmer P.O. Box 4675 Albuquerque, NM 87196-4675 Telephone: (505) 262-0911 Email: [EMAIL PROTECTED] WWW: http://www.digitalpriest.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
