text: **Web viewing considerations**
  When you choose a viewer strategy in web clients, it is important to know the differences 
  among the viewer architectures: 
  
  (cid:2) Java applet viewers, such as the line data applet or Content Navigator’s generic applet 
  
  viewer, are downloaded automatically to the user’s computer and run within the browser. 
  No deployment is needed, but a Java installation must be present on the PC. They are 
  effectively cached on the user computers, and they can provide sophisticated functionality. 
  On the downside, each Java applet requires a Java virtual machine (JVM) to run. On 
  terminal servers that serve multiple users at once, this requirement might lead to larger 
  memory consumption. 
  
  (cid:2) Plug-in viewers are native applications that must be installed through a setup routine on 
  
  the user’s computer. They integrate with the browser and provide their own viewing logic, 
  which can be sophisticated (for example, with the AFP plug-in). 
  
  (cid:2) The generic and Ajax viewers that are provided by Content Navigator provide limited 
  rendering and viewing capabilities. They do not require any rollout or JVM. 
  
  (cid:2) Transforms, such as the Ricoh AFP2PDF or other vendor-provided transforms, result in a 
  PDF document that is viewed in the Acrobat viewer. Although this viewer is deployed on 
  most user PCs, the rendering consumes processing power on the mid-tier system. Also, 
  large documents cannot be rendered into PDFs. Because the PDF is displayed by an 
  external application, it cannot communicate with the Content Manager OnDemand server 
  like the line data applet. 