Web-based Ranger development Q&A

Q: Are most applications that use Ranger thick clients or Web apps?
A: There is a mixture, but the majority of check scanning applications in our industry are "thick clients."

Q: How easy is it to develop Ranger-based Web applications?
A: It depends on the Web and check scanner development experience level of your programmers. Many find Ranger easy to work with when developing Web-based applications.

Q: How do Web applications handle the installation of Ranger and the scanner drivers? Via web interface, installation CD/file? Is there anything installed on the client PC?
A: Whether you use Ranger or not, you will need to install software on the Client PC. Check scanner manufacturers require that you install their device drivers and support software on local PC in order to use their scanners. Most Web-based applications require their users to download and run an installation program prior to running the check scanning Web application. The installation program installs the scanner drivers, Ranger, and any other software elements which requires administrator privileges to install.

Q: Why do developers use Web-based apps versus thick clients?
A: Web applications are easy to upgrade. Application changes on the Web Server automatically propagate to the Web Clients.

Q: Would you describe the installation and use of a Web-based Ranger application? How flexible is this with different scanners?
A: It is pretty much the same for all scanners. The device drivers and Ranger software are installed in the Client PC during the initial Web application setup process. You can implement the download and installation of this software in whichever way is most convenient to you.

Q: What languages are being used to develop Web-based Ranger apps?
A: Microsoft Web scripting languages seem to be the most common, followed by Java.

Q: How is data security handled in Web-based apps?
A: A common approach is to connect to the Web Server via secure sockets (SSL). Data transmitted over a SSL connection is encrypted by the TCP/IP subsystem.