This content has been marked as final. Show 6 replies
Doesn't the archive have to be a relative URI? Relative to the directory holding the HTML?
Well that didn't use to have to be the case, and I'm a bit miffed it seems to be enforced now. If I uncheck the use the the next-gen plugin, all works as I want it to; the next-gen plugin seems to want to rob me of my implementation freedom. Sign of the times?
I have recently found that using the applet caching mechanisms described here:
...can allow your applet to perform just as well when JAR files are loaded from the server (using the next-gen plugin), as when loaded from the file system (when not using the next-gen plugin).
Well that didn't use to have to be the caseThe rule has been there since at least 1997. Whether browsers enforced it or not is another question.
Sign of the times?Sign of complying with a 15-year-old specification. The next-generation plugin has been out for about five years too so I don't know what times you would be referring to.
I'm referring to today, actually. In the Java 7 Plugin on Windows 7 using IE 8, if the Next-Generation Plugin is NOT used, it is possible to use the file:/// protocol in the archive parameter to load local JAR files in an applet tag, even when the HTML describing this markup is loaded from a web server somewhere. When the next-generation plugin is checked, it seems the JAR files can only be loaded using HTTP.
I'm sure I'm not the only one that finds this a bit confusing, especially as we've been using file:/// to load local JAR files for at least 5 years in our application. Now we would like to use Java 7 and the next-gen plugin as that seems to be what all the cool kids are using, but it introduces additional complexity and slowness that tend to make me seriously wonder if Java Applets are worth bothering with, 'Next Generation' technology or not. Maybe it's just me and my own ignorance, but that's why I'm here asking for information...
931849 wrote:They're not and haven't been for a very long time. Why people other than game developers have bothered with them for so long has always puzzled me. I'd rather webstart a Swing application than use a bloody applet. JavaFX 2 is the new hot thing where Java in a browser is concerned in any case, its time to finally let Applets become a bad memory.
that tend to make me seriously wonder if Java Applets are worth bothering with, 'Next Generation' technology or not.
if the Next-Generation Plugin is NOT used, it is possible to use the file:/// protocol in the archive parameter to load local JAR files in an applet tagSeems like somewhat of a security hole to me that you can actually run stuff from the local machine, assuming you're still linking to it in a resource loaded through the internet. Especially because in this case we're talking about an actual program and not just something as silly and usually harmless as an image (not counting any exploits in PNG libs).
Good thing that the next-gen plugin no longer allows it.