The path of Java
Java circa 1995 had a ‘fat client’ architecture
- applet based distribution
- central application servers for download
- dynamic content on the client
Java circa 2000 provides a range of architectural options
- applets (fat client) or HTML forms (thin client)
- servlets / Java Server Pages / EJBs on the server
- + JDBC, RMI, SSI, etc.
Java is now serious e-business
- dynamic content is the key business goal
- how dynamic content is delivered is not a simple choice