JogAmp Deployment Enhancements: Automatic loading of native JARs (Applet/Application)

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

JogAmp Deployment Enhancements: Automatic loading of native JARs (Applet/Application)

Sven Gothel
Administrator
JogAmp Deployment Enhancements: Automatic loading of native JARs (Applet/Application)

Currently implemented in modules GlueGen and JOGL. TODO: JOAL and JOCL.

http://jogamp.org/deployment/jogamp-next/ points to curren beta build (signed)
  http://jogamp.org/deployment/archive/master/gluegen_410-joal_213-jogl_489-jocl_424-signed/

See NApplet:
  http://jogamp.org/deployment/jogamp-next/jogl-test-applets.html

Without the need for an applet launcher or JNLP extension,
or setting up the native library folder for applications,
we automatic cache the JAR file,
verify it's certificate (for non applications) and load the content.

As you can see in the documented html pages:
  http://jogamp.org/deployment/jogamp-next/jogl-applet-version-napplet.html
  http://jogamp.org/deployment/jogamp-next/jogl-applet-runner-newt-gears-normal-napplet.html

.. this simplifies the tag and need to write a JNLP file.

The native JAR download mechanism still benefits from the applet's
network cache mechanism, hence downloads the JAR only
  - if it doesn't exist, or
  - if the server version is updated

Of course, this causes a network connection but surely not a big deal
and more correct. Users can still use the JNLP mechanism of course
using the JNLP tag:
  <update check="background" policy="always"/>

Applications don't need to worry about the system dependent way
of dropping and publish the native lib folder anymore.
Applications also load the native JAR file and use their native libs,
just deploy all JARs in the same folder - done.

Git commits in this regard:
 - GlueGen from
     http://jogamp.org/git/?p=gluegen.git;a=commit;h=f357a00e511f0049865392adecc4d042663da6e6
   upto
     http://jogamp.org/git/?p=gluegen.git;a=commit;h=609e649443f900116039cda7a1bc7c9359b0242f

 - JOGL from
     http://jogamp.org/git/?p=jogl.git;a=commit;h=ac358bd66878e63a370377d4c7f625ec5b1b9e31
   upto
     http://jogamp.org/git/?p=jogl.git;a=commit;h=424a5ecbd7575eb39343638696c19cd617577912


This feature will be enabled in general for rc4 soon.

Please reply w/ your concerns and ideas etc,
so we can make this one work fine and secure for all.
 
Cheers, Sven
Reply | Threaded
Open this post in threaded view
|

Re: JogAmp Deployment Enhancements: Automatic loading of native JARs (Applet/Application)

Sven Gothel
Administrator
See NApplet, LApplet and Dual definition at
  http://jogamp.org/deployment/jogamp-next/jogl-test-applets.html

I have verified the new NApplet launcher method on Linux/Windows 64bit
w/ FF6 and Chrome (beta) and IE9 (windows only).

Works quite reliable for me.

Comparing NApplet w/ JApplet, Dual and LApplet it also launches faster
especially when reloaded (browser back/forth).