How “Remote Scan” Works in Dynamic Web TWAIN 12.0

Before we introduce about this new feature, let’s take a look at how Dynamic Web TWAIN HTML5 Edition works in previous versions.

without-remote-scan

As illustrated above, when an end user visits the document scanning page for the very first time, a Windows service is downloaded and installed on the client machine. This Windows service accepts user operation commands from a JavaScript client. It listens on localhost and handles the interface with TWAIN and passes the response to the JavaScript layer.

We can see that the Windows service and the JavaScript layer is on the same machine. Things are different with the new remote scan feature in the latest release. Below is a basic diagram.

remote scan with Dynamic Web TWAIN v12

From the illustration, we see that the web twain Windows service and the JavaScript client run on separate machines. The former needs to be installed on a PC or a Windows server. JavaScript client can be any device with a JavaScript-compatible browser installed, like, iPad, android, iPhone, Linux, etc. NO installation is required on the client machines.

A basic workflow:

  1. The JavaScript client initiates a scanning job to the website server.
  2. The website server sends a scan request to the Web TWAIN Windows service;
  3. The Windows service interacts with the scanner and retrieves the images;
  4. The Windows service sends the (compressed) data to the client machine;
  5. The JavaScript client uploads the images to a database server.

This kind of setup is especially useful for scenarios where a centralized document scanning server is available.

About how to get the new remote scan feature up and running, please refer to this knowledge base article: How to enable remote scan.

 

 

Subscribe Newsletter

Subscribe to our mailing list to get the monthly update.

Subscribename@email.com