Andrew said:
Exclude Java applets, or any Javascript, from
being *required* by the user agent. Base your
web-app around the assumption of 'HTML', but
*nothing* more..
A 'thin client' AFAIU, means an interface to
your (web) application that requires 'a browser'
and nothing more (no JS, no Java). (Guru's
..please correct me if I'm wrong)
AFAIU a thin client is Software OR Hardware which provides form of access to a system
Without doing any formal processing for system. The thin client only processes what it
needs to get display info and send back commands to the server
For example we use Sun Ray thin client hardware to provide a portable desktop environment
to a solaris Workstation.
The hardware in this case is basically just a network card/graphics card/sound card/usb
controller but does ALL my processing for actually running applications is done on the
workstation. The Thin client firmware and protocol engine transports all infomation from
the server to my desktop and back...
So a thin client is a very abstract term IMHO.
to implement a thin client you need a system which users need access to, hooks in the code
to allow remote interfaces to take part in a session, a remote client which can display
the session and send key/mouse events back and a protocol engine to transport all this
accross a network.
for example the above could be respectivley
Java Application
Servlet Container, EJB
Web Browser
HTTP
in my case is it
X server / XDMP
Sun Ray server
Sun Ray desktop Hardware
Sun Ray protocol.
HTH
Rob
whatever happened to the "internet appliance"