TWAIN is a standardized software protocol that gives a universal standard that communicates between applications and image acquisition devices, like scanners and digital cameras. As web applications become increasingly popular, many TWAIN applications also have to work with web applications.
This white paper is for software developers building web applications that acquire images from TWAIN-compatible devices through web browsers. The paper offers some rules to live by when looking for a TWAIN component. By simply following these rules you will find a solution that will save you time and enhance your productivity.
What to Look for when looking for Web Scanning Components
Easy to Develop
Rule #1: A web scanning component should make web development easier.
The TWAIN 2.1 specification is really a pain-staking 664 pages long. It can take weeks just to read through the document let alone get a full understanding of the specification. Additionally, once you’ve grasped TWAIN, the amount of work to enable image compression codec, like TIFF, JPEG or PNG, and image upload/download features can be overwhelming. As a result, creating a web scanning solution from the scratch is almost impossible.
Web Page Load Time
Rule #2: A web scanning component must be small for lightning-fast rendering.
When an end user visits a web page with the ActiveX/Plug-in component for the first time, the control must be downloaded from the web server to the user’s browser and then installed. The greater the control size, the longer it takes to download. Users’ patience for slow downloads is thin, so every second counts.
Image Upload Time