Hi Mark. I use H2 in EE development, but not as part of my Glassfish instance. I start H2 as a seperate database service (daemon) and then connect to it via TCP/IP. It does make it a tad slower due to TCP/IP overhead, but you really have to go way out to justify not doing this. In my scenarion, I like having the database run merrily on it's own, with the app server (Glassfish) now free to crash and burn as it likes. This makes for less worries during installation and even less worries during production. Now I have a database that my app server AND other applications can talk to. Not only do desktop applications pull reports from this database, but I also have a seperate application that connects to the database from time to time to gather statistics.
Best regards Ewald -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
