>I have thought about pulling the class out of 1.2, but was not certain of
>the affects. Additionlly, I thought of just rewrting their code in 1.1.7.
>Either way that is an option.
>
>The Jar will consist of classes the will be run as an
>application/applet/serialized bean. But for the performance part the
>applet is the big concern. Such a big jar, start off with big problems.
>
True, but I would argue that the actual performance of downloading the
entire jar onto the local VM each time the app starts is probably not that
big of a hit, and once it's there, there's no more need to go across the
wire. <shrug>
>Do you think the 1.1 security model will hamper a ClassLoader like that?
>
I don't think so, unless you're running as an applet--the
AppletSecurityManager disallows ClassLoaders of all forms.
>
>-Bob
>
>
>On Thu, 6 May 1999, Ted Neward wrote:
>
>> Robert--
>>
>> >Trying to optimize JAR performance. We have a JAR that is 700K using
>> >JDK1.1.7 and are looking for ways to improve the performance when using
>> >it. At this time we cannot migrate to Java2 and utilize the
>> >JArURLConnection. Does anyone have any suggestions? We would like to
>> >split the JAR into two JARs: 1 for GUI and one for CORE components but
>> >have run into difficultly due JAR loading at the 1.1 level. Additinoally,
>> >we have looked into client side install with class date checking sort of a
>> >Smart Update...
>> >
>> >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).
>>
>> Are your jars compressed? JDK 1.1 had a problem with compressed .jars, as I
>> recall, but I'm not 100% sure of that.
>>
>> Alternatively, I don't see any reason why you couldn't pull the source for
>> URLClassLoader out of 1.2, put it into your own "java2" package, and use it
>> within java 1.1..... You'd have to make a few source modifications to
>> adjust for the changed ClassLoader rules in 1.2, but that shouldn't be
>> rocket science.
>>
>> >Any past experience in this area would be helpful...
>> >
>> I haven't done this precise thing, but I've done a lot of work with
>> ClassLoaders; I'll be happy to help as best I can.
>>
>> Hope any of this rambling makes sense or helps out....
>>
>>
>> ----------------------------------------------------------------------
>> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>>
>
>
>
>----------------------------------------------------------------------
>To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
