On Thu, May 06, 1999 at 10:27:41AM -0700, Ted Neward wrote:
> From the context of what you're saying, I'm guessing that you're running a
> Java application and not an applet on the client. What I can suggest is
> that you write a custom ClassLoader that uses java.net.URL to connect to a
> given web server, check dates (against the .jar in your local path),
> download the .jar if necessary, then proceed with normal class loading
> (which is probably your "SmartUpdate" idea in a nutshell).
I've been looking for a way to provide users of my software with a
"SmartUpdate" feature. Your idea sounds great, the only problem is when
your want to save the new JAR in place of the old one: under Unix it
should work, but under windows the original JAR is locked and it is
impossible to squash it with the new one.
Would you have any idea on how to replace a JAR in-place and circumvent
file locking under some platforms? This problem has been bugging me for
more than a year.
TIA.
--
Louis-David Mitterrand - [EMAIL PROTECTED] - http://www.aparima.com
Conscience is what hurts when everything else feels so good.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
