sexta-feira, 2 de dezembro de 2016

NAPS2 + Twain

Just few works about the Twain.


http://www.twain.org/docs/54ac758f020c7b091adc2d52/Introduction-to-TWAIN-Direct.pdf


   //Improve Zoom better Quality
               drawEngine.g.InterpolationMode = System.Drawing.Drawing2D.InterpolationMode.High;




Image Capture APIs are complex, reflecting the native complexity of scanners, which
Introduction
to TWAIN Direct™
(DRAFT COPY)
5
TWAIN Working Group
often support a large number of possible settings

http://sourceforge.net/projects/twain-dsm/?source=typ_redirect
http://sourceforge.net/projects/wia-on-twain/?source=typ_redirect
http://sourceforge.net/projects/twain-dsm/?source=typ_redirect



Topics:

CMYK color model - Wikipedia, the free encyclopedia
ICC profile - Wikipedia, the free encyclopedia
Spectrophotometry - Wikipedia, the free encyclopedia
Tristimulus colorimeter - Wikipedia, the free encyclopedia


postgresql-8.3-607.jdbc3.jar
eclipselink-2.2.0.jar
gnu-crypto.jar
javax.persistence_1.99.0.jar
jtds-1.3.1.jar
ojdbc14-1.0.jar


using System;
using System.IO;
using System.Security;
using System.Security.Cryptography;
using System.Runtime.InteropServices;
using System.Text;

namespace CSEncryptDecrypt
{
   class Class1
   {
      //  Call this function to remove the key from memory after use for security
      [System.Runtime.InteropServices.DllImport("KERNEL32.DLL", EntryPoint="RtlZeroMemory")]
      public static extern bool ZeroMemory(IntPtr Destination, int Length);
            
      // Function to Generate a 64 bits Key.
      static string GenerateKey()
      {
         // Create an instance of Symetric Algorithm. Key and IV is generated automatically.
         DESCryptoServiceProvider desCrypto =(DESCryptoServiceProvider)DESCryptoServiceProvider.Create();

         // Use the Automatically generated key for Encryption.
         return ASCIIEncoding.ASCII.GetString(desCrypto.Key);
      }

      static void EncryptFile(string sInputFilename,
         string sOutputFilename,
         string sKey)
      {
         FileStream fsInput = new FileStream(sInputFilename,
            FileMode.Open,
            FileAccess.Read);

         FileStream fsEncrypted = new FileStream(sOutputFilename,
            FileMode.Create,
            FileAccess.Write);
         DESCryptoServiceProvider DES = new DESCryptoServiceProvider();
         DES.Key = ASCIIEncoding.ASCII.GetBytes(sKey);
         DES.IV = ASCIIEncoding.ASCII.GetBytes(sKey);
         ICryptoTransform desencrypt = DES.CreateEncryptor();
         CryptoStream cryptostream = new CryptoStream(fsEncrypted,
            desencrypt,
            CryptoStreamMode.Write);

         byte[] bytearrayinput = new byte[fsInput.Length];
         fsInput.Read(bytearrayinput, 0, bytearrayinput.Length);
         cryptostream.Write(bytearrayinput, 0, bytearrayinput.Length);
         cryptostream.Close();
         fsInput.Close();
         fsEncrypted.Close();
      }

      static void DecryptFile(string sInputFilename,
         string sOutputFilename,
         string sKey)
      {
         DESCryptoServiceProvider DES = new DESCryptoServiceProvider();
         //A 64 bit key and IV is required for this provider.
         //Set secret key For DES algorithm.
         DES.Key = ASCIIEncoding.ASCII.GetBytes(sKey);
         //Set initialization vector.
         DES.IV = ASCIIEncoding.ASCII.GetBytes(sKey);

         //Create a file stream to read the encrypted file back.
         FileStream fsread = new FileStream(sInputFilename,
            FileMode.Open,
            FileAccess.Read);
         //Create a DES decryptor from the DES instance.
         ICryptoTransform desdecrypt = DES.CreateDecryptor();
         //Create crypto stream set to read and do a
         //DES decryption transform on incoming bytes.
         CryptoStream cryptostreamDecr = new CryptoStream(fsread,
            desdecrypt,
            CryptoStreamMode.Read);
         //Print the contents of the decrypted file.
         StreamWriter fsDecrypted = new StreamWriter(sOutputFilename);
         fsDecrypted.Write(new StreamReader(cryptostreamDecr).ReadToEnd());
         fsDecrypted.Flush();
         fsDecrypted.Close();
      }


https://panicbutton.io/#how

      static void Main()
      {
         // Must be 64 bits, 8 bytes.
         // Distribute this key to the user who will decrypt this file.
         string sSecretKey;
        
         // Get the Key for the file to Encrypt.
         sSecretKey = GenerateKey();

         // For additional security Pin the key.
         GCHandle gch = GCHandle.Alloc( sSecretKey,GCHandleType.Pinned );
        
         // Encrypt the file.       
         EncryptFile(@"C:\MyData.txt",
            @"C:\Encrypted.txt",
            sSecretKey);

         // Decrypt the file.
         DecryptFile(@"C:\Encrypted.txt",
            @"C:\Decrypted.txt",
            sSecretKey);

         // Remove the Key from memory.
         ZeroMemory(gch.AddrOfPinnedObject(), sSecretKey.Length * 2);
         gch.Free();
      }
   }
}








"When to use Redis? 

Caching 

Caching using MongoDB simply doesn't make a lot of sense. It would be too slow. 

If you have enough time to think about your DB design. 

You can't simply throw in your documents into Redis. You have to think of the way you in which you want to store and organize your data. One example are hashes in Redis. They are quite different from "traditional", nested objects, which means you'll have to rethink the way you store nested documents. One solution would be to store a reference inside the hash to another hash (something like key: [id of second hash]). Another idea would be to store it as JSON, which seems counter-intuitive to most people with a *SQL-background. 

If you need really high performance. 

Beating the performance Redis provides is nearly impossible. Imagine you database being as fast as your cache. That's what it feels like using Redis as a real database. 

If you don't care that much about scaling. 

Scaling Redis is not as hard as it used to be. For instance, you could use a kind of proxy server in order to distribute the data among multiple Redis instances. Master-slave replication is not that complicated, but distributing you keys among multiple Redis-instances needs to be done on the application site (e.g. using a hash-function, Modulo etc.). Scaling MongoDB by comparison is much simpler. 

When to use MongoDB 

Prototyping, Startups, Hackathons 

MongoDB is perfectly suited for rapid prototyping. Nevertheless, performance isn't that good. Also keep in mind that you'll most likely have to define some sort of schema in your application. 

When you need to change your schema quickly. 

Because there is no schema! Altering tables in traditional, relational DBMS is painfully expensive and slow. MongoDB solves this problem by not making a lot of assumptions on your underlying data. Nevertheless, it tries to optimize as far as possible without requiring you to define a schema. 

TL;DR - Use Redis if performance is important and you are willing to spend time optimizing and organizing your data. - Use MongoDB if you need to build a prototype without worrying too much about your DB. "



Refer: http://stackoverflow.com/questions/5400163/when-to-redis-when-to-mongodb 


http://db-engines.com/en/system/Elasticsearch%3BRedis
Postar um comentário