Carefully considering the answers to that question could lead to significant redesign. A server failure that causes problems for a single client is not nearly as worrisome as one that causes problems for all active clients. Ask where you are saving state and what state will be lost if a server goes down. Make sure that your code is thread safe. Grosso recommended that you over-synchronize methods and then remove them when you're sure that you can.
Sluggish code is preferable to blocked code.
The idea of this code is that you make some call and you are returned a boolean value that tells you whether or not the operation was successfully performed. The problem with this code is that programmers tend to not check the returned value in subsequent code. Lewis took time to give clear and complete answers to all questions that were asked, and after ninety minutes was an hour behind schedule. He began by putting EJB components in the context of a well-defined J2EE application. A browser or application on the client tier uses HTTP to communicate with a JSP file in the second tier.