<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic HP-UX and sticky Java Applets in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-and-sticky-java-applets/m-p/3169164#M718104</link>
    <description>Thought this forum was worth a shot:&lt;BR /&gt;&lt;BR /&gt;Does anyone know if there is an advantage to using sticky java applets or cache file expiration dates if most of the class files needed to load our applets are already stored locally in a couple of client JAR files? &lt;BR /&gt;&lt;BR /&gt;FYI: Here is a description of sticky applet techology:&lt;BR /&gt;JRE 1.3 introduces an alternative form of applet caching which allows an applet deployer to decide her applet should be "sticky", that is, to stay on the disk in a secondary cache which the browser cannot overwrite. The only time "sticky" applets get downloaded after that is when they are updated on their server. &lt;BR /&gt;&lt;BR /&gt;I'm wondering whether I should look into either of those 2 for possible performance gains, as the applets still can be slow to load.&lt;BR /&gt;&lt;BR /&gt;We are using Java SDK 1.3.1_08 on HP-UX 11.0 servers.  Thanks for any info... &lt;BR /&gt;</description>
    <pubDate>Tue, 20 Jan 2004 19:34:24 GMT</pubDate>
    <dc:creator>Sheelah Brennan</dc:creator>
    <dc:date>2004-01-20T19:34:24Z</dc:date>
    <item>
      <title>HP-UX and sticky Java Applets</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-and-sticky-java-applets/m-p/3169164#M718104</link>
      <description>Thought this forum was worth a shot:&lt;BR /&gt;&lt;BR /&gt;Does anyone know if there is an advantage to using sticky java applets or cache file expiration dates if most of the class files needed to load our applets are already stored locally in a couple of client JAR files? &lt;BR /&gt;&lt;BR /&gt;FYI: Here is a description of sticky applet techology:&lt;BR /&gt;JRE 1.3 introduces an alternative form of applet caching which allows an applet deployer to decide her applet should be "sticky", that is, to stay on the disk in a secondary cache which the browser cannot overwrite. The only time "sticky" applets get downloaded after that is when they are updated on their server. &lt;BR /&gt;&lt;BR /&gt;I'm wondering whether I should look into either of those 2 for possible performance gains, as the applets still can be slow to load.&lt;BR /&gt;&lt;BR /&gt;We are using Java SDK 1.3.1_08 on HP-UX 11.0 servers.  Thanks for any info... &lt;BR /&gt;</description>
      <pubDate>Tue, 20 Jan 2004 19:34:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-and-sticky-java-applets/m-p/3169164#M718104</guid>
      <dc:creator>Sheelah Brennan</dc:creator>
      <dc:date>2004-01-20T19:34:24Z</dc:date>
    </item>
  </channel>
</rss>

