I would use EJB (Stateless Session Beans), this gives you a natural place to implement caching for data safety, it will let you have fail-over between app servers and is a standards-based solution. Plus there is a load of essentially ready to reuse code on the web (for the ServiceLocator, Delegate, Facade and other relevant J2EE patterns.
I'm using this in my app and am really pleased with the results. You can completely eliminate the client's need to know about DB connectivity, transactions, data safety, etc. You can implement a cache at the client side (in the delegate) for data safety and performance. -----Original Message----- From: J Aaron Farr [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 7:17 PM To: [EMAIL PROTECTED] Subject: OJB C/S Features Hello all. My group is looking for a database model solution and I think OJB might work, but after reading the documentation (which is great) I still have a few questions, mostly about the Client / Server features. Perhaps first I'll explain what we're looking for: 1. We have a lot of client applications (Swing based) which need database connectivity. Currently they each have a dedicated database connection via JDBC. We'd like to pool those those connections on the server side. 2. However, we can't afford to lose data. So currently each client has a local cache and if we lose network connectivity, the data is cached until we can upload it into the database. If we move to a connection pool we need to insure that if either the client or any remote pooling objects lose network connectivity, the data is properly cached. In other words, we need strong failover and transaction support. Now we could probably do an EJB solution, but I'd like to avoid EJB's if at all possible. I think OJB's client/server features with perhaps a few enhancements might meet our requirements. So here's what I'd like to know: (1) Is it possible to meet our requirements with OJB? (2) If not, what's missing? (I'm not afraid to submit patches and enhancements) (3) Are there any other open source projects that might be better suited for this? For example, I've looked at Turbine's JCS subproject for caching and I Avalon might have some components we could use. Thanks for your advice! The project looks great and I hope I get a chance to use it and contribute. J Aaron Farr <[EMAIL PROTECTED]> __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
