I might add that MYSQL's commercial license is very expensive. So expensive that it precluded its use in my case. It is true that Derby is not in the same league as MYSQL, but it is better than writing your own file system. I use Derby in both embedded and client-server applications. I was pleasantly surprised at the response time the client-server model gave me. It is used in a LAN application, but there was still no perceptable difference between the response time of the client-server and the embedded mode. It works great using a Windows client and a linux server. All the code is on the client machine and the server just has the Derby jar files. I have enhanced it as of late and added some administrative functions on the server written in Java with a GUI interface using the Swing Library.
Dan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, June 28, 2007 2:39 AM To: Derby Discussion Subject: Re: How to shutdown with authentication "Calvin (Yu-Hui) Liu" <[EMAIL PROTECTED]> writes: > Hi, Leonard, > > I'm new to derby so maybe this is a stupid question for you: why do > you want to use derby, especially use it as a network service? In > another word, what's the use case of you? It's reasonable for me to > use it as embedded db. But as long as we have more mature db like > mysql, I can't understand that. Could you please give me some clue? I can't answer for Leonard, obviously. But it could be beacuse: A) He wants to embed the db in a java app, but also let remote clients connect. B) It may because he wants to be sure that the DB runs anywhere Java runs. C) Maybe he needs to deploy his DB server on many different machines and likes that fact that he only needs to install a couple of jar files D) Maybe he cannot use MySQL's dual GPL/commercial licence for some reason. -- dt ********************************************************************** NOTICE: This e-mail, including attachments, contains information that may be confidential, protected by the attorney/client or other privileges, or exempt from disclosure under applicable law. Further, this e-mail may contain information that is proprietary and/or constitutes a trade secret. This e-mail, including attachments, constitutes non-public information intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this communication, please be advised that any disclosure, dissemination, distribution, copying, or other use of this communication or any attached document is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail and promptly destroy all electronic and printed copies of this communication and any attached documents. **********************************************************************
