I would like to add my experience to this thread. I am using UniObjects for Java with tomcat / glassfish.
Thread safety depends on where you place you UniSession object. If you create it in a method it is thread safe. If it is created in the class (HttpServlet ...) it is common to all processRequest calls and therefore not thread safe. You can leverage off the persistence and trim overhead by keeping a single connection open and allowing multiple clients to make requests. I have this implemented and working well at my company.
Just my 2 yen. Brutzman, Bill wrote:
Here is another design angle... Although we use MS Exchange and Outlook, Excel, and Word, my boss eschews Microsoft IE. As I am not looking to talk myself out of my job, I am not looking to force .net on him. --Bill ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
