This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: ClassLoader
- To: Kresten Krab Thorup <krab@gnu.org>
- Subject: Re: ClassLoader
- From: Geoff Berry <gcb@gnu.org>
- Date: 10 Aug 1999 11:09:45 -0400
- Cc: Per Bothner <per@bothner.com>, java-discuss@sourceware.cygnus.com
- References: <wxpiu6om41o.fsf_-_@harp.is.s.u-tokyo.ac.jp>
Kresten Krab Thorup <krab@gnu.org> writes:
[snip]
> It seems like JarURLConnection needs to be able to create a temporary
> file containg the jar file, in case it is coming from the net. The
> spec doesn't say explicitly. This is needed because JarURLConnection
> needs to provide a java.util.jar.JarFile instance of it's contents,
> and JarFile's only operate on RandomAccessFile's.
>
> The question is how to do this the best way. I'd actually prefer if
> the jar file would not have to be written to the file system at all.
> It seems like it would be sufficient to have an in-memory
> representation, and let swapping take care of the rest. The problem
> is, that there is no such thing as a RandomAccessByteArrayFile, or the
> like. So this is not realy a viable option.
Why not just use File.createTempFile and let the implementation deal
with having a file-system or not?
--
Geoff Berry