|
Nathan, EJBs have certainly improved and aggregation is one area that improvements were made but your example is where a lighter weight API like Hibernate or iBatis will perform much better. In general, you don't persist summarized data back to the original data model so EJBs are not helpful in this case although they will seriously impact performance. You can run into this situation with Hibernate but you don't have to leave the API to fix the performance problem. David Morris >>> nandel@xxxxxxxxxxxxxxxxxxx 3/9/2004 9:36:41 AM >>> David, ...Say a Servlet receives a request to summarize sales by state and display the results. The process of summarizing sales by state may be a fairly CPU intensive activity that needs to be synchronized per user. Using EJBs, summarizing sales by state might be dispatched to one processor, while generating the HTML might be dispatched to another, so that when multiple requests are received at the same time, the 2nd isn't waiting for the 1st to complete... Nathan.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.