|
> From: David Gibbs > > Well, true 5250 devices don't ... but who uses a real 5250 anymore? Well, the two places I mentioned. And if you go to Client Access, you get back to deployment issues and platform specificity. There are alternatives, but they get progressively more feature-poor. > What about a Java applet? Easy deployment model, rich control set, > security (assuming I understand the sandbox concept correctly). Seems > like a very reasonable compromise between a pure browser interface and a > fat client. I've got lots of clients who have tried using applets, and none who have succeeded. It can be done, but the practical drawbacks seem to outweigh the theoretical benefits. For example, you have to code back to the lowest supported JDK. There are some places where they seem to work acceptably - usually small, single-purpose tasks. IBM's navigation applet for InfoCenter is an example. But I haven't seen any successful large scale implementations of an applet-based interface. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
