Glossary

212 views 0

Activation key

Entering the activation key in License Manager enables unlimited application of the ThinPrint software. An activation key is obtained by submitting license and registra­tion keys to ThinPrint GmbH.

AutoConnect

ThinPrint component for automatic connection to printer shares of print servers; it can be run on any Windows machine.

Bandwidth

The capacity of a network or data connection for digital transmission, usually mea­sured in bit/second (bit/s, bits/sec, or bps) or in Kilo-bit/ second (kbit/s, kbits/sec, or kbps).

Bandwidth control

A ThinPrint Port regulates bandwidth for print jobs. Because bandwidth is controlled separately per printer port and can be set individually, optimal performance can be achieved with the following ThinPrint settings:

  • Number of ThinPrint Ports
  • Different bandwidth settings for each ThinPrint Port
  • Assignment of printers to ThinPrint Ports
Class

see Printer Class

Client

The term client signifies a device which connects to, requests data from, and / or starts an application on, a server. It receives, for example, print data from the server and forwards it to a printer. Typical clients are: workstations, notebooks, thin clients, print servers, gateway appliances and network printers.

Client Gateway

see Gateways

COM

Component Object Model; fundamental communication model for icon communica­tion under Windows.

Compression

In addition to bandwidth control, ThinPrint compresses print data. Typical compres­sion rates for PCL and Postscript printer drivers lie somewhere between 55 % and 95 % – depending on printer driver, application, and type of data (e. g.: pixel/vector fonts, pixel/vector graphics). With Driver Free Printing there are four available com­pression options (high image compression, good compression, high image quality, lossless compression). Nonetheless, when printing with either Driver Free Printing, or with the native printer driver, a higher or lower compression may be chosen with­out compromising the print quality (Configuration).

Connected Gateway

see Connection Service

Connection Service

Connection Service enables printing to ThinPrint Clients that are hidden behind Net­work Address Translation (NAT). But in contrast to Virtual Channel Gateway the print data is sent over pure TCP/IP and not via an RDP, ICA or PCoIP channel.

ThinPrint Engine sends all print jobs to the Connection Service, which passes them on to the ThinPrint Clients. No IP addresses are used for addressing the ThinPrint Clients, but rather a ThinPrint specific Client ID. This Client ID is created in ThinPrint Client.

Current printer

A setting in the ThinPrint Client Manager: A document is printed with the current printer if a client has only one printer, or no printer ID was given with addressing. Current printer can also be used to set the default printer at the server when using AutoConnect (with the option Default at Server).

Data type

Several types are usually supported for printing using Windows. The two most com­monly used – expanded metafile (EMF) and print-ready (RAW) – affect performance on both client and print server machines differently. See also EMF.

Dedicated print server

A served “dedicated” to a single task: printing. A terminal server, virtual desktop or workstation does not send print data directly to clients, but to central, dedicated print servers. There it is rendered, and then sent to the clients or printers. (see also Print server)

Device

Here: thin client, print server, printer (print device), gateway / print appliance or print server (print box)

EMF

EMF (enhanced metafile) is the default data type for most Windows programs. Unlike those in RAW format, printed documents in EMF are converted to metafile format.

With Driver Free Printing, EMF files are smaller than RAW files containing the same print job. In server-based computing, only the first half of a print job is gener­ated on the terminal server or virtual desktop (for the sake of system performance). The main work is performed by the client machine, thus improving the terminal server’s or virtual desktop’s performance. See also Data type.

Encryption

see TLS

Gateways

ThinPrint uses the following kinds of gateways:

  1. ThinPrint Output Gateway: ThinPrint’s virtual printer driver
  2. Virtual Channel Gateway: With our Virtual Channel Gateway, we actually put print data coming from a print server into the RDP, ICA or PCoIP virtual channel and send it directly to the client.
  3. ThinPrint Client Gateway: Local print server with installed ThinPrint Client
ICA

Independent Computing Architecture (from Citrix); network protocol for communica­tion between Windows terminal servers (or virtual desktops) and ICA clients.

ICA is a 3-part technology for server-based computing, that separates application logic from the user interface, and allows the application to run entirely on the server.

ICA requires Citrix XenApp on the server; XenApp requires Microsoft Terminal Ser­vices.

IP masking

see Network Address Translation

License key

All ThinPrint software requires a license key. The key has the format: TLUS-xxxx-x-xxxxxx-xxxx. License Man­ager uses the license key to generate a registration key according to system configu­ration. Both the license key and the registration key are required to request the acti­vation key.

Local resources

Local in this sense means available to or installed upon the selected computer. Client operating systems always search first for a local printer driver. Thus, when printing on the client side, the printer driver is first sought on the client computer, and only if necessary, is a driver downloaded from the server.

LPD client

An LPD client is a network end device that supports the Line Printer Daemon (LPD); e. g., an internal or external print server of a network printer, or a Linux terminal. It is also possible to print with ThinPrint to LPD devices, even if there is no ThinPrint Cli­ent available there. Although compression cannot be used, bandwidth control is available to improve printing in this environment.

LPD filter

An LPD filter is run on LPD clients to decompress print jobs which have been pro­cessed by ThinPrint.

LPR

Line Printer Remote; Program for issuing a print job (client component of LPD)

Network Address Translation (NAT)

Multiple private addresses are transformed into a single public IP address. This lets several workstations in a LAN use the IP address for Internet access, while the LAN hides behind the router’s IP address, as registered in the Internet.

Output Gateway

see Gateways

Port pooling

see the section Port pooling

Print device

Contrary to popular nomenclature, hardware which produces printed material is called a print device and NOT a printer. Print resolution is measured in DPI (Dots Per Inch). The higher the DPI value, the better the resolution. See also Printer

Printer

The point of interface between operating system and print device is called the printer. In Windows architecture alone, many possible terms exist: logical printer, printer soft­ware, or printer object. Printer settings include, among other, the designation of a connection (i. e., LPT1 or ThinPort), the printer driver (this is normally included by the manufacturer), authorization of share names, etc. In Windows, every printer is represented in the printers folder or in the Print Management by an icon with an obvi­ous name.

There is generally not a one-to-one relationship between printer and print devices. Several printers for a single print device, for example, signify that either the print device is connected to several computers, or that many printers have been set up on a computer, with different parameters for the same print device.

For better understanding, this description only distinguishes between printers, printer objects, and print devices when the specific context makes it necessary.

Printer class

Printers whose drivers are compatible can be grouped in a class. For example, many laser printers are compatible with HP LaserJet (class could be: HPLaser). Only one entry in Dynamic Printer Matrix of AutoConnect is necessary for all printers in a class.

Printer driver

Printer drivers are programs which enable communication between client applica­tions and print devices. Each print device requires unambiguous commands which are specific to that device, to employ such print functions as color, margin, format, etc. An operating system comprehends these individual commands for specific print devices through the printer driver.

Printer object

In Windows: a printer created in the printers folder or in the Print Management.

Printer pool

see Port pooling

Printer queue

The list of documents which are ready to be printed from a particular print device, and / or are waiting for processing, is referred to, in Windows terminology, as the printer queue. Under NetWare and OS/2, the term printer queue is synonymous with printer.

Printer software

Printer software is the commonly used name for logical printer or printer.

Print job

Print jobs are composed of a source code in the language of the relevant printer. This source code contains both print data, such as a text or picture, and print device com­mands such as form feed or page format.

Print server

A print server is hardware which connects print devices with a network. The print server is thus responsible for the printer queues of connected print devices. A print server can also be a specific hardware device that exclusively embodies the network connection, plus a serial or parallel connection (print appliance / external print server / print box). A print server can also be pre-integrated within a printer, so that separate hardware is unnecessary and the print device can be directly connected with the network (internal or onboard print server). (see also Dedicated print server)

Print server services

Print server services is the term for the print server software that handles communi­cation with non-Windows clients. Because a print job from a UNIX client is different than one from a Macintosh client, there are different print server services. These can, for instance, change the parameter for data type, as needed.

Print spooler

see Spooler

Queue

see Printer queue

RDP

Remote Desktop Protocol; communication protocol between Remote Desktop Ses­sion Hosts or virtual desktops and clients, in a Windows operating system. The name of the service is Terminal Services, and the connection type in Windows is called Remote Desktop Connection.

Remote Desktop Connection

see RDP

Remote Desktop Services

see Terminal Services

Remote Desktop Session Host

see Terminal server

Rendering

A printer driver is used to translate a print job into printer-specific format.

Server based Com­puting

A server-centric system for facilitating user access to applications. Application logic is run on a server or virtual desktop, and only the user interface is transmitted through the network. See also Terminal server

Session-in-Session

When printers are assigned by AutoConnect in a terminal session, they are still avail­able if a further session is configured from a terminal server, onto another machine.

Spooler

Print spooler describes those programs or DLLs (Dynamic Link Libraries) which together, receive, process, temporarily save, chronologically sort, and distribute queued print jobs.

With network printers, the spooler has a client component and a server compo­nent. The client component is normally found where the application is being run. The server component is generally where the print device is installed, for example, at the print server (Windows service denomination: Print Spooler).

Spooling

Simultaneous Peripheral Operations On-Line: Print jobs are temporarily stored as files on a hard disk. This procedure is known as spooling and is only one of the several functions of the spooler. Unspooling is the process of reading this file and sending it to the print device.

SSL

see TLS

Terminal server

= Remote Desktop Session Host: a Windows server with Microsoft Terminal Services or Remote Desktop Services

Terminal Services

= Remote Desktop Services: a Windows service for remote desktop sessions

Thin client

A minimum performance computer with only elementary hardware and / or software components (no hard drive)

In a server/client architecture, a client system on which no application programs are run. Instead, all applications are processed at the server.

ThinPrint Client

On the client side, ThinPrint Client is generally responsible for receiving print data, decompressing and decrypting it, and sending it to the print device. Many ThinPrint Clients are available for different end devices and areas of deployment: for all Win­dows versions, for Mac OS and Linux as well as for internal or external print servers of network printers.

ThinPrint Client Gateway

see Gateways

ThinPrint Client Service Windows

The Windows service version of ThinPrint Client is automatically started when a cli­ent machine is activated. Thus, it is not necessary for a user to be logged on for the Client Service Windows to function. This ThinPrint Client is therefore particularly well suited for local print servers under Windows (ThinPrint Client Gateways). ThinPrint Client Service Windows does not support print preview with Driver Free Printing.

ThinPrint Connec­tion Service

see Connection Service

ThinPrint Engine

The server component ThinPrint Engine is the actual core of the ThinPrint framework. It provides complete printer driver management, including Driver Free Printing. The ThinPrint Engine performs the following main functions:

  • Bandwidth controlled transmission of print jobs
  • Print data compression and streaming
  • Print data encryption
  • Provides the virtual printer driver ThinPrint Output Gateway (enabling a radical reduction of printer drivers on printing computers = Driver Free Printing).
ThinPrint Output Gateway

see Gateways

ThinPrint Port

To print with ThinPrint, printers are linked to ThinPrint Ports on the machine that cre­ates the print jobs. These printer ports are created and configured with the MMC. It is, however, not necessary to create a port for every printer; many printers can be configured to the same port. With port pooling, however, one or more printers are connected to several ports.

ThinPrint Virtual Channel Gateway

see Gateways

ThinShare

see the Print data compression 

TLS

To establish a secure connection with SSL / TLS, the communication partners must first agree on the cryptographic methods and parameters to be used. Basically, SSL / TLS offers the options of key exchange, systematic encryption, and the calcula­tion of a cryptographic proof sum. There are various methods that can be used for each of these options.

Since SSL is now obsolete, ThinPrint prefers encryption with TLS, but still sup­ports SSL 3.0.

V-Layer

Printing with ThinPrint Output Gateway

Virtual Channel Gateway

see Gateways

x64

Identifies all 64-bit processors from Advanced Micro Devices (AMD) as well as Intel processors with an AMD compatible 64-bit extension (e. g. Xeon and Pentium with EM64T). In contrast ia64 identifies the 64-bit processor Itanium from HP and Intel.

XenApp

Server-based software (Citrix) for Microsoft Terminal Services

Previous Page
Next Page

Was this helpful?