This topic contains 2 replies, has 0 voices, and was last updated by khk 1 year, 3 months ago.
Viewing 3 posts - 1 through 3 (of 3 total)
-
Posts
-
Viewing 3 posts - 1 through 3 (of 3 total)
Forums › TWAIN Direct › Using TWAIN Direct for browser based scanning
This topic contains 2 replies, has 0 voices, and was last updated by khk 1 year, 3 months ago.
Hello,
I am building a browser based application to perform document scanning. I have looked at TWAIN Direct user guide and understood that TWAIN Direct should be the route to implement such applications. Need some more clarity on following.
1. Application will invoke RESTful APIs to leverage scanner functions. Who is responsible for implementing RESTful APIs on server side? Is it TWAIN- local that does this or do scanner vendors implement this?
2. Is TWAIN-local a component that one could directly use?
3. Is TWAIN Direct ready for production deployments?
Request inputs on these to help me understand further.
We have been using a library called Scanner.js on some of our intranet apps with great success.
FYI, It’s browser based with TWAIN classic, and it’s a JavaScript API instead of RESTful.
hio