Hi all, Just signed up to the ol' ranch. Of late i have been hearing more and more about AJAX/web 2.0, thing is i cant really see what the fuss is about, surely what you can do with AJAX can be done with an Applet?
Which leads to the question, is browser support for applets more consistant then it once was when the only examples of applets where to show how to do animation on the web? (Yes i am showing my age )
Anyway hope you are all enjoying a happy new year.
I have seen some very amazing things done with applets lately. If you can ensure that your clients install the Java plugin from Sun, which isn't a sure thing, well, then you can do some amazing stuff.
I worked on a project where a portal server (JetSpeed) delivered portlet that were really just Applets. The applets could communicate back to the server without having to refresh the page. It was pretty amazing, combining the best of the portal environment, with the best of Java applets. I really hope it catches on.
Applets are still more fat than they are phat though. Perception is a big problem.
Gavin, one of the benefits of AJAX would be that you're working with a web page, and can manipulate its layout and content to your hearts content. Once an applet is loaded its size is fixed, and its layout as well to a degree. (The layout can of course be changed, but it's not anywhere near as flexible as manipulating the DOM of a web page.) And, unfortunately, what Cameron said is very true: Having a properly installed recent JVM in a browser is not a given.
Cameron, was what you saw a public web site that you could point us to? I'd be quite interested to see it.
Originally posted by Gavin Tranter: I was just thinking, that to my mind, AJAX applications are client application running within a browser, so I was just thinking: "if its an application why not use applets? As both load in a browser."
I was expecting JVM's across browser to be, "standard" by now.
Thanks for the insights
In fact, the distinction is almost non-existant, as you can regard it as adding scripting to the HTML.
Another point I think AJAX has over applet is that it can be built on any middle-ware which has power to throw HTML pages. Its not exactly true with Applet as it needs server port which can understand http and serve http response. I meant it will become complicated if applet wants to talk to some middle layer which is written in lets say ASP.
love your job and not your company;
...because you never know when your company will stop loving you!
Joined: Mar 22, 2005
Applet as it needs server port which can understand http and serve http response
Applets can communicate with the host using any protocol they want - it doesn't need to be HTTP. That's actually a benefit they have over AJAX, which can only communicate using HTTP.
But applets likely won't talk to an ASP (or PHP) application precisely because that most likely emits HTML, with which the applet can't do all that much. It's more common that an applet would talk to a specialized server that does not emit HTML, but data in some form the applet can understand, and present in its GUI accordingly. That server could be a servlet, but needn't be. [ January 02, 2007: Message edited by: Ulf Dittmer ]
The top and left side are applets, which communicate with the browser using LiveScript. The applet communicates with the server using serialized Java commands tunneled through HTTP. Portlet configurations, such as a text portlet shown in the screenie, uses Java dialogs.
It works for Windows, Mac, Linux and Solaris clients. Since it's a reasonably controlled environment we require Java Plugin 1.4.2+, and a reasonably new browser.
The applet jar is 10Mb, but with 1.5 it's down to only a couple of megs due to the new compression scheme. Applet caching is a must-have due to the size, obviously.
All in all, pretty cool. Having fancy icons makes it look non-Swing too :-)