Relativity

 Relativity – Imaging Documents

In relativity, you can convert group of doc to images using imaging porofile and sets

·         Image output DPI

·         Color Image – yes/No

·         Image Size : Converts a document to an image that fits with the selected page dimension.This feature will resize images when they are larger tgan the selected page size , using the aspect ratio to maintain image proportion. When an image is of the same size or smaller no change will be made to it.

o    Use page setting : uses current document size for image conversion

o    Letter (8.5 in X 11 in)

o    A4 (8.27 in X 11.69 in)

o    Legal (8.5 X 14 in)

o    Custom Size

·         Maximum Image Height (inches) / Maximum Image Width (inches) -  largest allowed size for geneartion of custom image

Relativity is using web services (web service URL for the native imaging server in the configuration table)

Word Processor is the category for common word processing formats such as Word, WordStar, Word-Perfect, and others. (Additional super types are Database, Spreadsheet, Graphic, Multimedia,and Other.)

Maximum pages imaged per file is a native global setting for all document types that sets the

maximum number of document pages that are imaged. For example, if you set this value to 50

and have a 100-page document, only the first 50 pages of the document will be imaged. Use this

option to image only the number of pages entered in this box.

Time Zone Field on Document determines what time zone will be used to display dates/times

in a document image. If no selection is made here, the time zone will default to Greenwich Mean Time

(GMT).

Node.js – javascript api to run programs on server

single-threaded approach to event-driven programming is different from what I know today

1. When a client browser initiates an HTTP request for a resource on the Web server, HTTP.sys intercepts the request.
2. HTTP.sys contacts WAS to obtain information from the configuration store.
3. WAS requests configuration information from the configuration store, applicationHost.config.
4. The WWW Service receives configuration information, such as application pool and site configuration.
5. The WWW Service uses the configuration information to configure HTTP.sys.
6. WAS starts a worker process for the application pool to which the request was made.
7. The worker process processes the request and returns a response to HTTP.sys.
8. The client receives a response.

When WAS starts a worker process (w3wp.exe) the worker process allocates a thread for loading and executing your application. This is analogous to starting a program and inspecting the process in Windows Task Manager. If you open 3 instances of the program, you will see 3 processes in task manager and each process will have a minimum of one thread. If an unhandled exception occurs in the program, the entire process is torn down, but it doesn’t affect other processes because they are isolated for each other.

Processes, however, are not free. Starting and maintaining a process requires CPU time and memory, both of which are finite, and more processes and threads require more resources.

.NET improves resource consumption and adds an additional degree of isolation through Application Domains or AppDomains. AppDomains live within a process and your application runs inside an AppDomain.

You’ve created two ASP.NET applications on the same server, and have not done any special configuration. What is happening?

A single ASP.NET worker process will host both of the ASP.NET applications. On Windows XP and Windows 2000 this process is named aspnet_wp.exe, and the process runs under the security context of the local ASPNET account. On Windows 2003 the worker process has the name w3wp.exe and runs under the NETWORK SERVICE account by default.

An object lives in one AppDomain. Each ASP.NET application will have it’s own set of global variables: Cache, Application, and Session objects are not shared. Even though the code for both of the applications resides inside the same process, the unit of isolation is the .NET AppDomain. If there are classes with shared or static members, and those classes exist in both applications, each AppDomain will have it’s own copy of the static fields – the data is not shared. The code and data for each application is safely isolated and inside of a boundary provided by the AppDomain

In order to communicate or pass objects between AppDomains, you’ll need to look at techniques in .NET for communication across boundaries, such as .NET remoting or web services. 

As outlined in steps 1 – 7 above, when a request comes in, IIS uses an I/O thread to dispatch the request off to ASP.NET. ASP.NET immediately sends the request to the CLR thread pool which returns immediately with a pending status. This frees the IIS I/O thread to handle the next request and so on. Now, if there is a thread available in the thread pool, life is good, and the work item is executed, returning back to the I/O thread in step 7. However, if all of the threads in the thread pool are busy, the request will queue until a CLR thread pool thread is available to process the work item, and if the queue length is too high, users will receive a somewhat terse request to go away and come back later.

This is a bit of an extreme trivialization of what happens. There are a number of knobs that can be set in IIS and ASP.NET that allow you to tune the number of concurrent requests, threads and connections that affect both IIS and the CLR thread pool. For example, the IIS thread pool has a maximum thread count of 256. ASP.NET initializes its thread pool to 100 threads per processor/core. You can adjust things like the maximum number of concurrent requests per CPU (which defaults to 5000) and maximum number of connections of 12 per CPU but this can be increased. This stuff is not easy to grasp, and system administrators dedicate entire careers to getting this right. In fact, it is so hard, that we are slowly moving away from having to manage this ourselves and just paying some really smart engineers to do it for us, at massive scale.