Received: from gemini.cybersurf.net (root@gemini.cybersurf.net [209.197.128.8]) by hub.org (8.8.8/8.7.5) with ESMTP id TAA22599 for ; Tue, 21 Jul 1998 19:12:59 -0400 (EDT) Received: from cybersoft.ab.ca (pc19.cybersurf.net [209.197.128.39]) by gemini.cybersurf.net (8.8.7/8.8.7) with ESMTP id RAA30243; Tue, 21 Jul 1998 17:12:52 -0600 Message-ID: <35B520ED.EF94D035@cybersoft.ab.ca> Date: Tue, 21 Jul 1998 17:14:53 -0600 From: Dallas Hockley Organization: Cybersoft Communications Software Inc. X-Mailer: Mozilla 4.5b1 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Peter T Mount CC: Jeffrey Napolitano , Interface to PostgreSQL Subject: Re: [INTERFACES] "static" libraries? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Peter T Mount wrote: > > On Tue, 21 Jul 1998, Jeffrey Napolitano wrote: [BIG snip] > > > The down side to this is that if a newer version of the driver is > > > released, then you have to rebuild your application jar file. > > > There is another method that _may_ work, YMMV, as I haven't tried it in this contect myself. There is a URL class loader, which can in essence load the driver class from a jar file referenced by a URL and served up by a web server on the network. It's not unlike loading the Driver class locally, and you can then have a central distribution point (or points) for the driver. Just an idea... Dallas Hockley hockleyd@cybersoft.ab.ca