Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 97628 invoked from network); 30 Sep 2007 14:12:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Sep 2007 14:12:33 -0000 Received: (qmail 13439 invoked by uid 500); 30 Sep 2007 14:12:22 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 12995 invoked by uid 500); 30 Sep 2007 14:12:22 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 12984 invoked by uid 99); 30 Sep 2007 14:12:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Sep 2007 07:12:21 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [206.190.39.154] (HELO web51011.mail.re2.yahoo.com) (206.190.39.154) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 30 Sep 2007 14:12:22 +0000 Received: (qmail 58294 invoked by uid 60001); 30 Sep 2007 14:12:00 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=FgeraoA8wkQHaHPvG2lO0HelIpwm14hHcI6ytXA4W8VGno7JBS51hV4g6mzWqpEVwnOLohTPfVRE/BroyljXuc1oZtDP8jmCPvA6b8Pw+Ru1cRkVbazBA1f4jUKkz6i/e2OY0a/6aIqf3yiDmwVpsYrRZVRoFw61tjQpN6gCoL4=; X-YMail-OSG: 60yibZgVM1ldV_1tl27gIHVxIis9_2NbDdPAhDfC8_VMKUV1spEoMIp_bQdsSQoABw-- Received: from [76.18.34.140] by web51011.mail.re2.yahoo.com via HTTP; Sun, 30 Sep 2007 07:12:00 PDT Date: Sun, 30 Sep 2007 07:12:00 -0700 (PDT) From: Christopher Nagel Subject: Client-side network server start/stop? To: derby-user@db.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <519422.58169.qm@web51011.mail.re2.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, I am just learning about Derby, and trying to do so *fast* so I can adopt it without impacting my deadlines. So I apologize for the "noob"-ality of this post. But I have read the dev-guide and the admin-guide and the code examples. I need a common resource that is never dependent on network connectivity. So I thought, have each client host a server: If no Derby server is up, start one. If the fileserver is up, Derby serves the central database on the NAS to all the other clients. If the NAS is down, serve a replicated local copy. The client connects to its own Derby server. Other clients connect to the first Derby server. If the Derby server goes down (when that first user quits the app), another client has to take over (this is the hardest part, right?). Is this even worth attempting? Is this as abnormal as it seems to me? Can anyone suggest how best to make it happen? Thanks! Looking forward to really learning Derby - it's way cool! Chris ____________________________________________________________________________________ Catch up on fall's hot new shows on Yahoo! TV. Watch previews, get listings, and more! http://tv.yahoo.com/collections/3658