You might want to give Pack200 a try; it's a Java classfile-aware compression
algorithm that can produce jars that are far more compact than e.g. if you were
to only gzip applet jars on their way out to your users. Lots of info about it
if you feel like googling.
Using a build from the
My company (read: I) develop an web-based educational application (a
language lab) implemented as a Java applet.
I have spendt the summer porting it to Clojure. I am very happy with
the results.
Except: The download (and therefore the download-time) has increased
dramatically, as I now include
Hi,
There is a slim version of the clojure jar. See here for example here:
http://repo1.maven.org/maven2/org/clojure/clojure/1.3.0-beta1/
Sincerely
Meikel
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to
The slim jar probably won't work in an applet, because it does classloader
stuff (unless you have a signed applet).
--
Dave
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts
Yes. My applet is signed. So that is not a problem.
Any thoughts about difference in performance between slim and
full?
My applet mostly does swing-stuff, http GETS and POSTS - and audio
playback and recording.
On 25 Aug, 10:40, David Powell d...@djpowell.net wrote:
The slim jar probably
The runtime performance should be the same, but the startup time will be
slower because it will have to compile the clojure code at load time.
--
Dave
On 25 Aug 2011 12:15, Terje Dahl te...@terjedahl.no wrote:
Yes. My applet is signed. So that is not a problem.
Any thoughts about difference
My company (read: I) develop an web-based educational application (a
language lab) implemented as a Java applet.
I have spendt the summer porting it to Clojure. I am very happy with
the results.
Except: The download (and therefore the download-time) has increased
dramatically, as I now
