Now, "there is no FREE lunch" there are problems of various categories using the applet... 1. what if you want to do session management. there is no direct functionality in Applet to do it...this applies to situations where your applet is going to used by many persons and you want to have state stored (i remember questions of this sort in JavaRanch sometime ago). 2. biggest issue is Java Runtime environment + Browser issues + API compatibility issues (specially with JDK1.4) (you would find problems arising due to OBJECT/EMBED tags in this forum in combination with NN4.7/7 and IE issues) 3. using "java.policy" file would have to be handled in such a manner that the end user doesn't end up spending time understand "whys" and "whats" and "where" and you know... 4. Applet restrictions applies if its not signed and we have to live with things that are available if we can't make applet signed somehow.. (due to monetory issues and other issues) 5. support issues (though it can be overcome) on Windows XP due to corporate fights... Other please feel free to add to this list as well..
posted 17 years ago
posted 17 years ago
Session management is no real problem. I was delighted to discover that things like session cookie-handling are automagically taken care of using the URLConnection to do http tunneling - no session code need be written, it simply inherits from the container (browser). One of the BIGGER problems with applets was that the browser standard was an antique pre-Swing version. Or worse, for people starting with Win/XP from scratch, none at all. Sure you CAN tell people they have to download a 5MB plug-in, but WILL they? However, thanks to Monday's judicial ruling, Windows may end up supporting JDK1.4 whether they like it or not, and that in turn puts pressure on other platforms to move into the 21st Century (literally!).
"privilege" comes from the Latin words for "private" and "law" (legal) and dates to feudal times. To "claim privilege" meant that you were above the laws that applied to the common people.