Saturday, January 4, 2003, 10:10, you wrote: >> At first, we tried to use 0.9.8 in our application. Because many >> clients access the data in one database we decided straightforward >> to use 3-tier architecture without an application server. An >> application server would be overkill for our small application.
> The OJB c/s mode is not necessary for such a scenario. Just run all > your clients in singlevm mode. You will still have proper > transaction isolation in this mode! > OJB c/s mode is meant as a means to provide scalability for > AppServer based applications. It should be used as a last resort > only if there is no other way to scale the app server machine. In > your case there is no such scalability bottleneck, as you don't want > to use an application server. (of course the db could also become a > bottleneck, but OJB c/s won't help here too!) http://jakarta.apache.org/ojb/index.html: "In standalone mode (or single VM mode) the OJB PersistenceBroker is running in the same Java VM as the client application. This is useful if only one instance of the client application is running (e.g. in applications with a local database or in single-server Servlet- or EJB applications). This is the default mode." I thought this means that the database is available at the same time for only one client - the part "applications with a local database" of the quote above was a misleading description for me. So, nothing gets in the way of using OJB - fine. Yours sincerely, Martin Burger -- >> netbeyond D. Barth & M. Burger GbR Im Stadtwald, Geb�ude 34.2 66123 Saarbr�cken Tel.: +49 (0)700 netbeyond +49 (0)700 63 82 39 66 Fax : +49 (0)681 3 02 63 84 Mail: [EMAIL PROTECTED] Web : www.netbeyond.de -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
