Software Code Help

What will be the use of Impersonation in ASP.NET?

2010-01-22T11:21:33.238+05:30

At times users access a resource as though they were someone else. This is known as impersonation. For example, if a web page has no access controls, then any user can access that web page. HTML pages, ASP pages, and components in version 3.0 and earlier can be accessed through two accounts named IUSR_machinename and IWAM_machinename. Both the accounts are set up during IIS installation, and are automatically added to all the folders in every web site on the server.

Anonymous access to a resource in IIS makes the task of identifying a user extremely difficult. But there is no need to authenticate a user in the case of IIS. When IIS receives a request for a web page or other resource that has permission for anonymous access, IIS treats the IUSR_machinename account as the user's account, to access the resources. If the resource requested by the user is an ASP page that uses a COM or COM+ component, that component is executed using the IWAM_machinename account.

In ASP.NET, when impersonation is turned off, the resources can be accessed using a "local system process" account. When impersonation is turned on, ASP.NET executes every resource using the account of a specified user who is authenticated when the user makes the request. If you specify the IUSR_machinename account to be used as the user account, then ASP.NET will behave like previous versions of ASP, in providing access to the resources.

In ASP.NET, you first need to check whether the application is configured to use impersonation. In the case of IIS, the IIS impersonates users with its own IUSR account. In the case of ASP.NET, impersonation is used to decide whether the user's request should be executed using the account of the requested user, or that of a local system-process account that ASP.NET uses for anonymous requests.

The concept of impersonation is complex to some extent due to the fact that ASP.NET uses the dynamic compilation features of the .NET Framework. The IUSR account has only limited permissions on the local machine, and so is not suitable without some reconfiguration. This account is also used by IIS to access resources like HTML pages, documents, and zip files that are not executed as part of the .NET Framework.

If impersonation is enabled in an ASP.NET application then:
• If anonymous access is enabled in IIS, the request is made using the IUSR_machinename account.
• If anonymous access is disabled in IIS, the request is made using the account of the authenticated user.
• In either case, permissions for the account are checked in the Windows Access Control List (ACL) for the resource(s) that a user requests, and a resource is only available if the account they are running under is valid for that resource.

If impersonation is disabled in an ASP.NET application then:
• If anonymous access is enabled in IIS, the request is made using the system-level process account.
• If anonymous access is disabled in IIS, the request is made using the account of the authenticated user.
• In either case, permissions for the account are checked in the Windows ACL for the resource(s) that a user requests, and a resource is only available if the account they are running under is valid for that resource.

What are the different type of JIT compiler?

2010-01-22T11:18:19.831875+05:30

a) PRE JIT : It Compiles complete source code to native caode In a single Compilation.

b) ECONO JIT : It compiles only those methods that are called at Runtime.

c) NORMAL JIT : It compiles only those methods that are called at Runtime and are stored in cache.

What is Association, Aggregation and Composition?

2010-01-22T11:15:21.613125+05:30

Association represents the ability of one instance to send a message to another instance. This is typically implemented with a pointer or reference instance variable, although it might also be implemented as a method argument, or the creation of a local variable.

Aggregation is the typical whole/part relationship. This is exactly the same as an association with the exception that instances cannot have cyclic aggregation relationships (i.e. a part cannot contain its whole).
The fact that this is aggregation means that the instances of Node cannot form a cycle. Thus, this is a Tree of Nodes not a graph of Nodes.

Composition is exactly like Aggregation except that the lifetime of the 'part' is controlled by the 'whole'. This control may be direct or transitive. That is, the 'whole' may take direct responsibility for creating or destroying the 'part', or it may accept an already created part, and later pass it on to some other whole that assumes responsibility for it.

What is XSLT and Xpath?

2010-01-22T11:09:19.06625+05:30

XSLT is a rule based language used to transform XML documents in to other file formats. XSLT are nothing but generic transformation rules which can be applied to transform XML document to HTML, CS, Rich text etc. the XSLT processor takes the XML file and applies the XSLT transformation to produce a different document.

XPATH It is an XML query language to select specific parts of an XML document. Using XPATH you can address or filter elements and text in a XML document. For instance a simple XPATH expression like "Invoice/Amount" states find "Amount" node which are children of "Invoice" node.

What is the main difference between MSML and .NET Framework XML classes?

2010-01-22T11:03:56.94125+05:30

MSXML supports XMLDOM and SAX parsers while .NET framework XML classes support XML DOM and XML readers and writers.

MSXML supports asynchronous loading and validation while parsing. For instance you can send synchronous and asynchronous calls to a remote URL. But as such there is not direct support of synchronous and asynchronous calls in .NET framework XML. But same can be achieved by using "System.Net" namespaces.

Which are the namespaces in .NET used for XML?

2010-01-22T11:02:19.285+05:30

"System.xml.dll" is the actual physical file which has all XML implementation. Below are the commonly used namespaces:-

√ System.Xml

√ System.Xml.Schema

√ System.Xml.XPath

√ System.Xml.Xsl

What is XSL?

2010-01-22T11:00:50.56625+05:30

XSL (the eXtensible Stylesheet Language) is used to transform XML document to some other document. So its transformation document which can convert XML to some other document. For instance you can apply XSL to XML and convert it to HTML document or probably CSV files.

What is CDATA and CSS section in XML?

2010-01-22T11:00:19.75375+05:30

All data is normally parsed in XML but if you want to exclude some elements you will need to put those elements in CDATA.

With CSS you can format a XML document.

What is well formed XML & valid XML?

2010-01-22T10:59:16.00375+05:30

If a XML document is confirming to XML rules (all tags started are closed, there is a root element etc) then it’s a well formed XML.

If XML is confirming to DTD rules then it’s a valid XML.

What is DTD (Document Type definition)?

2010-01-22T10:58:11.87875+05:30

It defines how your XML should structure. For instance in the above XML we want to make it compulsory to provide "qty" and "totalcost", also that these two elements can only contain numeric. So you can define the DTD document and use that DTD document with in that XML

Can you explain why your project needed XML?

2010-01-22T10:54:34.831875+05:30

Note: - This is an interview question where the interviewer wants to know why you have chosen XML. Remember XML was meant to exchange data between two entities as you can define your user friendly tags with ease. In real world scenarios XML is meant to exchange data. For instance you have two applications who want to exchange information. But because they work in two complete opposite technologies it’s difficult to do it technically. For instance one application is made in JAVA and the other in .NET. But both languages understand XML so one of the applications will spit XML file which will be consumed and parsed by other applications You can give a scenario of two applications which are working separately and how you chose XML as the data transport medium.

Is XML meant to replace HTML?

2010-01-22T10:53:55.894375+05:30

No, they both go together one is for describing data while other is for displaying data.

What is the difference between XML and HTML?

2010-01-22T10:52:08.37875+05:30

XML describes data while HTML describes how the data should be displayed. So HTML is about displaying information while XML is about describing information.

Is XML case sensitive?

2010-01-22T10:51:37.66+05:30

Yes, they are case sensitive.

If XML does not have closing tag will it work?

2010-01-22T10:51:13.50375+05:30

No, every tag in XML which is opened should have a closing tag.

What is XML?

2010-01-22T10:50:13.144375+05:30

XML (Extensible markup language) is all about describing data. Below is a XML which describes invoice data.

<? xml version="1.0" encoding="utf-8"?>
<Product>
   <productname>Shoes</productname>
   <qty>12</qty>
   <totalcost>100</totalcost>
   <discount>10</discount>
</Product>>

An XML tag is not something predefined but it is something you have to define according to your needs. For instance in the above example of invoice all tags are defined according to business needs. The XML document is self explanatory, any one can easily understand looking at the XML data what exactly it means.

Short summary on Design Pattern.

2010-01-20T12:18:52.528+05:30

In software engineering (or computer science), a design pattern is a general repeatable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved. Algorithms are not thought of as design patterns, since they solve computational problems rather than design problems.

Design patterns can be classified in terms of the underlying problem they solve.

Creational Patterns -- concern the process of object creation.
Abstract Factory	Provide an interface for creating families of related or dependent objects without specifying their concrete classes.
Builder	Separates the construction of a complex object from its representation so that several different representations can be created, depending on the needs of the program.
Factory Method	Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation
Prototype	The Prototype pattern starts with an instantiated class and copies or clones it to make new instances. These instances can then be further tailored using their public methods.
Singleton	The Singleton pattern is a class of which there can be no more than one instance. It provides a single global point of access to that instance.

Structural Patterns -- describe how classes and objects can be combined to form larger structures.
Adapter	Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldn't otherwise because of incompatible interfaces.
Bridge	Decouple an abstraction from its implementation so that the two can vary independently.
Composite	Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and Compositions of objects uniformly.
Decorator	Attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassing for extending functionality.
Facade	Provide a unified interface to a set of interfaces in a subsystem. Façade defines a higher-level interface that makes the subsystem easier to use.
Flyweight	Use sharing to support large numbers of fine-grained objects efficiently.
Proxy	Provide a surrogate or placeholder for another object to control access to it.

Behavioral Patterns -- characterize the ways in which classes or objects interact and distribute responsibility
Chain of Resp.	Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.
Command	Encapsulate a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.
Interpreter	Given a language, define a representation for its grammar along with an interpreter that uses the representation to interpret sentences in the language.
Iterator	Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation.
Mediator	Define an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.
Memento	Without violating encapsulation, capture and externalize an object's internal state so that the object can be restored to this state later.
Observer	Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.
State	Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.
Strategy	Define a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from clients that use it.
Template Method	Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. Template Method lets subclasses redefine certain steps of an algorithm without changing the algorithm's structure.
Visitor	Represent an operation to be performed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operates.

The definitive Acronym list

2010-01-20T10:49:02.9033782+05:30

1MW 1 Microsoft Way
1TBS 1 True Brace Style
21D teach yourself ___ in 21 Days
3COM COMputer, COMmunication, COMpatibility
3Dwm 3-Dimensional Window Manager
3G 3rd Generation
3GIO 3rd Generation Input/Output
3GL 3rd Generation Language
3LD 3rd-Level Domain {IANA}
3NF 3rd Normal Form (databases)
3W World Wide Web
4GL 4th Generation Language
4WCD 4 Wire Conditioned Diphase
A/D Analog/Digital
A/UX Apple UniX
A2A Application TO Application
AA Administrative Authority
AA AntiAliasing
AAA Administration, Authorization, and Authentication (security)
AAA Asp Application Aggregator
AAAI American Association for Artificial Inelligence
AAB All-to-All Broadcast
AAC Advanced Audio Coding
AAEPS Anywhere Anytime Email Proxy Server
AAF Advanced Authoring Format
AAL Atm Abstraction Layer
AAMOF As A Matter Of Fact {chat}
AAP Application Access Point
AARP Appletalk Address Resolution Protocol {Apple}
AART Aggregate Average Response Time
AAS All-to-All Scatter
AAS Auto Area Segmentation
AASE Associate Accredited Systems Engineer {Compaq}
AASP Ascii Asynchronous Support Package
AAT Average Access Time
AAUI Apple Attachment Unit Interface {Apple}
ABA Address Book Archive
ABAP Advanced Business Application Programming
ABC A Bit Cypher
ABC Atanasoff-Berry Computer
ABCPP ABC PreProcessor
ABEL Advanced Boolean Expression Language
ABEND ABnormal END
ABGP
ABI Abstract Binary Interface
ABI Adaptive Brain Interface
ABI Application Binary Interface
ABIOS Advanced Basic Input/Output System
ABIST Automatic Built-In Self Test
ABLE Adaptive Battery Life Extender
ABM Anything But Microsoft
ABM Asynchronous Balanced Mode
ABNF Augmented Backus Normal Form
ABNF Augmented Backus-Naur Form
ABR Area Border Router
ABR Auto Band Rate
ABR Available Bit Rate
.
.
.
And retrieve the complete list fromt the attached Word document.

The definitive Acronym list.doc (1.06 MB)

Good General Interview Question.

2010-01-18T14:05:21.809+05:30

TYPES OF QUESTIONS

1. Close-ended questions. These questions may sometimes be helpful when an interviewer(s) wants to know certain information at the onset or needs to determine specific kinds of knowledge. Example: "Could you name the five specific applications involved in...?"

2. Probing questions. These questions allow the interviewer(s) to delve deeper for needed information. Example: "Why?", "What caused that to happen?", or "Under what circumstances did that occur?"

3. Hypothetical questions. Hypothetical situations based on specific job-related facts are presented to the applicant for solutions. Example: "What would you do if..", "How would you handle..."

4. Loaded questions. These questions force an applicant to choose between two undesirable alternatives. The most effective way to employ a loaded question is to recall a real-life situation where two divergent approaches were both carefully considered, then frame the situation as a question starting with, "What would be your approach to a situation where...".

5. Leading questions. The interviewer(s) sets up the question so that the applicant provides the desired response. When leading questions are asked, the interviewer cannot hope to learn anything about the applicant.

6. Open-ended questions. These are the most effective questions, yield the greatest amount of information, and allow the applicant latitude in responding. Example: "What did you like about your last job?"

Examples of open-ended effective probing:

1. What are/were the three main responsibilities in your current/last position? Which responsibilities do/did you enjoy the most? Why?

2. Of the three main responsibilities, which do/did you enjoy the least? Why?

3. Describe your supervisor's management style. Did/Do you like his or her style of management? Why or why not?

4. Describe your particular style of management, or the style of management you would choose if you were a manager.

5. In the past have you worked in a team environment or independently? Which did you prefer and why?

6. What amount of hours do you/ did you put in at your current/last position? How did you feel about working those hours?

7. What are three of your strongest work related qualities and how were you able to demonstrate these on your job?

8. What are three areas, with regard to your work, that you would like the opportunity to develop?

9. Why did you/are you leave/leaving your last/present position?

10. Of all the jobs you've held, which one did you like the most and why?

11. What major problems have you encountered so far in your professional life and how did you deal with them?

12. What have you learned from your mistakes?

13. How do you react to pressure?

14. What types of decisions are most difficult for you?

15. How have your prior experiences and education prepared you for this job?

16. What has been your biggest work-related frustration to date? How did you handle the situation?

17. Have you ever supervised anyone in a work setting? Have you ever hired or fired anyone?

18. What experience do you have in this field? How have you prepared yourself to switch fields?

19. How have you influenced productivity and results in your previous work experiences?

20. How have you prepared yourself to assume the challenges of this position?

21. How do your current skills apply to this position?

22. In what ways do you expect your relationships with current peers to change? How will you manage this shift?

Repeated Questions break rehearsed answers

1. What did you like about your previous job/manager?

2. What else did you like about your previous job/manager?

Difference between Session state nad View state ?

2010-01-18T11:32:46.097+05:30

In some cases, using view state is not feasible. The alternative for view state is session state. Session state is employed under the following situations:

o Large amounts of data - View state tends to increase the size of both the HTML page sent to the browser and the size of form posted back. Hence session state is used.

o Secure data - Though the view state data is encoded and may be encrypted, it is better and secure if no sensitive data is sent to the client. Thus, session state is a more secure option.

o Problems in serializing of objects into view state - View state is efficient for a small set of data. Other types like DataSet are slower and can generate a very large view state.

How to match Two Hexadecimal value switch is On or OFF in C#

2010-01-14T15:57:06.012+05:30

I have tested it using window application of C#, In this we have two Hexadecimal value, And we check that the source value exists in our database or not.

        public Test()
        {
            InitializeComponent();

//8 Byte Hexadecimal Value of source
this.txtSource.Text ="0x00004000";

            //8 Byte Hexadecimal Value of DB
            this.txtDB.Text ="0xAF00D0b0";
        }

        privatevoid button1_Click(object sender, EventArgs e)

        {
            //Convert the Hexadecimal value inot uint.
            uint i = GetHexValue(txtDB.Text.ToString());
            uint b = GetHexValue(txtSource.Text.ToString());

            txtResult.Text = (i & b) > 0 ? "Match" : "UnMatch";
        }

        //This is the function used for returning uint value from hexadecimal value.
        publicuint GetHexValue(String text)
        {
            uint result = 0;
            String parseText = text;
            if (parseText.StartsWith("0x", true, CultureInfo.InvariantCulture))
            {
                parseText = text.Substring(2);
            }

            if (UInt32.TryParse(parseText, NumberStyles.AllowHexSpecifier, CultureInfo.InvariantCulture, out result) == false)
            {
                thrownew ArgumentException("Text value must be a valid hexidecimal number"+ text);
            }

            return result;
        }

What are the means of conceptual data model, logical data model and physical data model?

2010-01-14T11:26:21.941+05:30

There are three levels of data modeling. They are conceptual, logical, and physical. This section will explain the difference among the three, the order with which each one is created, and how to go from one level to the other.

Conceptual Data Model

Features of conceptual data model include:

Includes the important entities and the relationships among them.
No attribute is specified.
No primary key is specified.

At this level, the data modeler attempts to identify the highest-level relationships among the different entities.

Logical Data Model

Features of logical data model include:

Includes all entities and relationships among them.
All attributes for each entity are specified.
The primary key for each entity specified.
Foreign keys (keys identifying the relationship between different entities) are specified.
Normalization occurs at this level.

At this level, the data modeler attempts to describe the data in as much detail as possible, without regard to how they will be physically implemented in the database.

In data warehousing, it is common for the conceptual data model and the logical data model to be combined into a single step (deliverable).

The steps for designing the logical data model are as follows:

Identify all entities.
Specify primary keys for all entities.
Find the relationships between different entities.
Find all attributes for each entity.
Resolve many-to-many relationships.
Normalization.

Physical Data Model

Features of physical data model include:

Specification all tables and columns.
Foreign keys are used to identify relationships between tables.
Denormalization may occur based on user requirements.
Physical considerations may cause the physical data model to be quite different from the logical data model.

At this level, the data modeler will specify how the logical data model will be realized in the database schema.

The steps for physical data model design are as follows:

Convert entities into tables.
Convert relationships into foreign keys.
Convert attributes into columns.
Modify the physical data model based on physical constraints / requirements.

When you leave company and send Good Bye Letter to your friends

2010-01-11T16:37:15.997+05:30

Hi My Team,

It’s really painful to leave you all; you all have made my path to grow in Company Name Love, support, care, faith everything that I received from my team will always be with me and I hope I’ll be in your memories for a very long time, specially when one will see “yellow error page” due to framework.

One thing I would love to say is, we all are very lucky for having such an admirable leader who seldom acts as lead but as a guardian always, so thanks a lot Lovely sir for everything you did, for your support and faith, I wish one day I’ll join you again.

I’ll try my best to be in touch, but if I failed I hope you people will keep me in touch.

All the best for you all!!!

Soon I’ll update you with my new contact no., my mail id is: Your Email Address

What are the meaning of Conceptual Design, Logical Design and Physical Design?

2010-01-07T11:24:42.144+05:30

Conceptual Design

A conceptual design is an abstract or high level design which includes only the most important components and entities. The main goal of a conceptual design is to provide an understandable picture of the overall purpose of the proposed solution. Components may include major technology systems, external systems that are required for integration or overall functionality, high level data flow, and system functionality. Think of this as the "black box" diagram where portions of the diagram may be simply a technology component to-be-named-later but is identified with its role and purpose.

Logical Design

A logical design is a more detailed design which includes all major components and entities plus their relationships. The data flows and connections are detailed in this stage. The target audience is typically developers or other systems architects. However, it is possible to create logical designs for business purposes to ensure that all components and functionality is accounted and well understood. Logical designs do not include physical server names or addresses. They do include any business services, application names and details, and other relevant information for development purposes.

Physical Design

A physical design has all major components and entities identified within specific physical servers and locations or specific software services, objects, or solutions. Include all known details such as operating systems, version numbers, and even patches that are relevant. Any physical constraints or limitations should also be identified within the server components, data flows, or connections. This design usually precludes or may be included and extended by the final implementation team into an implementation design.

What will be the use of private constructor in C#?

2010-01-04T11:13:02.269+05:30

A private constructor is a special instance constructor. It is commonly used in classes that contain static members only. If a class has one or more private constructors and no public constructors, then other classes (except nested classes) are not allowed to create instances of this class.

What are the core functionalities in XML .NET framework? Can you explain in detail those functionalities?

2010-01-01T11:07:07.113+05:30

The XML API for the .NET Framework comprises the following set of functionalities:

XML readers: With XML readers the client application get reference to instance of reader class. Reader class allows you to scroll forward through the contents like moving from node to node or element to element. You can compare it with the "SqlDataReader" object in ADO.NET which is forward only. In short XML reader allows you to browse through the XML document.

XML writers Using XML writers you can store the XML contents to any other storage media. For instance you want to store the whole in memory XML to a physical file or any other media.

XML document classes XML documents provides a in memory representation for the data in an XMLDOM structure as defined by W3C. It also supports browsing and editing of the document. So it gives you a complete memory tree structure representation of your XML document.

Terms & Defination used in Travel Domain?

2009-12-29T17:03:33.29775+05:30

A-type HIP	See HIP processing definition
AAP Options	WORLDSPAN Agent Assisted Pricing options. These options, append to 4P entries, can force a particular fare construction.
Africa	Comprises of Central Africa, Eastern Africa, Indian Ocean Islands, Libya, Southern Africa, Western Africa
Airline Pricing Profile	WORLDSPAN Internal Table controlling Carrier Specific preferences addressing specific issues, i.e. Fare Construction Application.
Area 1 (TC1)	All of the North and South American Continents and the adjacent Islands; Central America, Greenland, Bermuda, the West Indies and the islands of the Caribbean Sea, the Hawaiian Islands (including Midway and Palmyra)
Area 2 (TC2)	All of Europe as defined below and adjacent islands; Iceland. the Azores, all of Africa and adjacent islands, Ascension Island, that part of Asia lying west of and including Iran.
Area 3 (TC3)	All of Asia and the adjacent islands except that portion included in Area 2; all of the East Indies, Australia, New Zealand, and the adjacent islands of the Pacific Ocean, except those included in Area 1.
Back Haul	A fare construction applied to a fare sector to determine the minimum applicable fare, only when all of the following conditions apply: a. the journey is a one way journey, or an open jaw journey where the surface break is *neither* in the country of origin, country of turnaround, or both, and b. a higher intermediate fare is assessed, and c. a higher intermediate point exists from the point of origin to a stopover point in the fare component
Backhaul Minimum	The additional amount that must be added to a fare calculation as the result of a backhaul calculation.
Central Africa	· Malawi, Zambia, Zimbabwe
Circle Trip (CT)	Travel from a point and return thereto by a continuous, circuitous air route, including journeys comprising of two or more than two fare components , where in the outbound and inbound fare amounts (including mileage surcharges and higher intermediate fares) are not the same and do not meet the conditions of the round trip definition. Travel from one point and return to the same point by a continuous, circuitous air travel: where travel from and to the same point for which different inbound and outbound fare apply in the lowest class of service used and/or, where a higher intermediate point or mileage surcharge is assessed, and/or where more than two fare components apply for the journey

Circle Trip Minimum (CTM)	The additional amount that must be added to a fare calculation as the result of a circle trip minimum calculation.
Circle Trip - Normal Fare	Travel from a point and return by a continuous, circuitous air route by use of two (2) or more components. Closed journeys comprising two (2) fare components, only which do not meet the conditions of a round trip are also considered to be circle trip.
Circle Trip - Special Fares	Travel from a point and return thereto by a continuous, circuitous air route, comprising only two international fare components which do not meet the conditions of a round trip definition; provided that where no reasonable direct scheduled air route is available between two points, a break in the circle trip between two fare construction points may be traveled by any other means of transportation without prejudice to the circle trip. (per draft amendment from May’97 RAP meeting)
Combination	Whenever two or more one way or round trip or half round trip fares are used and shown separately in a fare calculation.
Common Point Minimum (CPM)	A fare construction applied to a fare sector to determine the minimum applicable fare, only when all of the following conditions apply: where a journey comprises not more than two international fare components with a Domestic Surface Sector and travel is via a Common Ticketed Point in the Country of Origin/Turnaround, the fare for the entire journey shall not be less than the applicable fare, from/to such common points
Component	A fare break point.
Constructed Fare	Unspecified through fares created by the use of add-on amounts, ot two or more fares shown as a single amount in a fare calculation.
Continent	For travel purposes, continent refers to a political grouping of countries, and does not necessarily correspond geographically.
Continental USA	the 48 contiguous States and the District of Columbia (this does not include Alaska, Hawaii)
Country of Commencement of Transportation	The country from which travel on the first international sector take place
Country of Payment	The country where payment is made by the purchaser to the TC Member or its Agent; payment by check, credit card or other banking instruments shall be deemed to have been made at the place where such instrument is accepted by the TC Member or its Agent
Country of Unit Origin	The country in which the unit origin is situated
Currency of the Country of Payment	The currency in which international fares from that country are denominated
Destination	The ultimate stopping place of the journey as shown on the ticket.
Differential	The difference between normal fares for the higher and lower classes of service for the segments(s) where the higher class of service is flown.
Direct Route
Direct Route Fare	The fare applicable to the direct route between two points, without regard to actual routing or stopover. When no direct route fare exists between two ticketed points a fare must be established by combination over a ticketed point on the itinerary.
Direct Route
Eastern Africa	· Burundi, Djbouti, Eritrea, Ethiopia, Kenya, Rwanda, Somalia · Tanzania, Uganda
EC Member States	· Austria , Belgium, Denmark, Finland, France, Germany, Greece · Iceland, Ireland, Italy, Luxembourg, the Netherlands · Portugal, Spain, Sweden, the United Kingdom
End on Combination (EOE)	Combination of two or more fares which could be ticketed separately at a fare construction point. (not applicable to combination of fares between the same points)
Fare Applicable	For Fare construction purposes, a fare which is established after the application of all fare construction calculations, e.g. excess mileage fare , higher intermediate fare
Fare Break Points	see Fare Construction Points
Fare Component (FC)	The portion of an itinerary between two fare construction points. (these are also termed fare break points)
Fare Construction Points	The manner in which fare break points have been determined.
Fare, Direct	For fare construction purposes, a fare component (these are also termed fare break points)
Far so Far (FSF)	The total accumulated fare for a priceable unit including HIPs and mileage surcharges.
Global Indicator (GI)	The global routing applicable to the fare as shown in IATA Attacment ‘A’ to RESO 011 The global routing applicable to the fare, as shown in the fare display. A sample listing is illustrated below: AF - via Africa AP - via the Atlantic and Pacific (via Area 1) AT - via the Atlantic EH - within the Eastern Hemisphere FE - via the Far East PA - via the South, Central, or North Pacific PO - via the North Polar route T3 - between the USSR and South East Asia / Japan / Korea; between Moscow and the South West Pacific TS - via Siberia (MOW) and/or nonstop between Europe and Japan / Korea

Half Round Trip Fares	Normal Fares - One half of the round trip published amount between two points , or the one way published amount between two points when no round trip is published. Special Fares - One half of the published round trip amount between two points, or the one way published amount whenever that one way fare may be doubled to establish a round trip fare.
Higher intermediate Point (HIP)	A ticketed point between origin and destination of a fare sector for which a higher fare is published.
HIP Processing	Higher Intermediate Point Processing is used to determine if an International through trip's fare is exceeded by any intermediate point's fares. There are four (4) types of HIP checks: A-type compares fares from origin to intermediate points with the fares for the whole trip. B-type compares fares from intermediate points to an offpoint with the fares for the whole trip. C-type compares fares between intermediate points with the fares for the whole trip. CP or P-type is a common point check. Occurs only in open - jaw itineraries. Compares fares from common point to other ticketed points in a trip. NOTE a common point doesn't have to be a stopover.
Indian Ocean Islands	· Comoros, Madagascar, Mauritius, Mayotte, Reunion, Seychelles
Industry Product Codes	An WORLDSPAN in-house method used to establish a hierarchy of fare type values.
Interline Transfer	Transfer from the service of one carrier to the service of another carrier
International Transfer	A change from the international service of one carrier to another international service of the same carrier (online transfer) or to the international service of another carrier (interline transfer)
Intermediate Ticketed Point	Any ticketed point other than the origin or destination of a fare sector.

International Sales Indicator Codes (ISI)	One of four codes that must be included in the origin and destination box of each international ticket. SITI/SITO/SOTI/SOTO For the purpose of determining ticketing transaction codes, the United States and Canada, or Denmark, Norway, and Sweden shall be considered on country.
	S I T I Indicates the sale and ticket issuance are both in the country of commencement of transportation. SITI will also apply to tickets:
	S I T O Indicates the sale is made in the country of commencement of transportation and ticket issuance is outside the country of commencement of transportation.
	S O T I Indicates the sales is outside the country of commencement of transportation and the ticket issuance is in the country of commencement of transportation.
	S O T O Indicates the sale and ticket issuance are both outside the country of commencement of transportation.
Journey	Origin to destination of the entire ticket.
Local Combination	Combination of fares between the same points
Local Currency Fares	Fares and related charges expressed in the currency of the country of commencement of travel; see RESO 024a for those countries where the US Dollar is used for local currency
Maximum Permitted Mileage (MPM)	Miles published in connection with a fare, governing the maximum distance a passenger is allowed to travel enroute between two particular points at the direct fare.
Non-IATA Carrier	Any carrier who is not a Member of IATA
Non-TC Member	A Member of IATA who has elected not to participate in Tariff Coordinating Conferences
Normal Fare (NL)	The full fare established for First, Business, or Economy class of service. Fares with no limited ticket validity or other restrictions with the possible exception of transfers, stopovers, or seasonality.
North America	(for WORLDSPAN pricing) Alaska, Canada, Continental USA, and Hawaii.
Neutral Units of Construction (NUC)	The neutral unit of construction used in fare construction.
OFF trip	Within minimum processing, the OFF trip is the remainder of the priceable unit, i.e. the portion that is not part of the HIP trip.

One Way (OW)	Considered to be any journey which, for fare calculation purposes, is not a complete round trip , circle trip, or other than round trip / circle trip (open jaw).
One Way Subjourney	Part of a journey wherin travel from one country does not return to such country and for which the fare is assessed as a single pricing unit using a one way fare (effective with PUC 6/1/00)
On-Line Transfer
Open Jaw, Normal	Travel from one country and return thereto with a domestic surface break in one country either at unit origin or unit turnaround, or a surface break at both unit origin and unit turnaround (per draft amendment definition from May’97 RAP meeting) In this context: · turnaround open jaw shall mean whee the outward point of arrival in the country of unit turnaround and the inward point of departure in the country of unit turnaround are different. · origin open jaw shall mean where the outward point of departure in the country of unit origin and the inward point of arrival in the country of unit origin are different. Except: · for travel originating in Canada and USA, the surface break may be permitted between countries in the Europe Sub-area: provided travel in both directions is via the Atlantic. · Canada, USA shall be considered as one country. · Denmark, Norway, and Sweden are considered on country.
Open Jaw - Special Fares	travel comprising two (2) international fare components whereby · for turnaround open jaw the outward point of arrival and the inward point of departure are different, or · for origin open jaw the outward point of departure and the inward point of arrival are different, or · for single open jaw either a) or b) applies, or · for open jaw any combination of the above may apply.
Origin	The initial starting place of the journey as shown on the ticket
Priceable Unit	A journey or part of a journey which is priced as a separate entity, e.g. is capable of being ticketed separately. A complete journey, if a single Pricing Unit , or part of a journey which is priced as a separate entity (is capable of being ticketed separately). A pricing unit comprises a single One Way fare component or a complete Round Trip / Circle Trip / Open Jaw Fare.
Return Subjourney	Part of a journey wherein travel is from a point / country and return thereto and for which the fare is assessed as a single pricing unit using half-round-trip, circle trip, normal fare open jaw; all applicable to special fare open jaw returning to the same of another country (effective with PUC 6/1/00)

Round the World (RTW) Differing Global Indicators	Travel from the point of origin and return thereto which involves only one crossing of the Atlantic Ocean and only one crossing of the Pacific Ocean.
Round Trip (RT)	(excluding Round the World - RTW) A journey comprised of not more than two fare components, from one point and return to the same point. When determining if a round trip journey exists, the applicable normal fare (including mileage surcharges and higher intermediate fares) both outbound and inbound must be equal, regardless of construction. If the fares to be used differ through class of service / seasonality / midweek-weekend / carrier variations, the outbound fare shall be used also for the inbound fare component for the purpose of determining if the journey is a round trip.
Routing	The carrier(s) and cities by and between which transportation is provided.
Scandinavia	Denmark, Norway, Sweden
Side Trip	Travel from and/or to an enroute point of a fare component.
Side Trip Combination	The combination of a fare which could be ticketed separately from and/or to an enroute point of a fare component.
Significant Carrier	The carrier whose fares are applicable for a fare component.
Significant segments	The flight segment used in international pricing which makes a travel conference (TC) break, country, continent, or sub-continental change.
South Africa
Special Fare (SP)	Any fare other than a normal fare
Specified Fare	A fare in an IATA Tariff Conference Resolution
Subjourney	A subjourney is a self-contained One Way / Round Trip / Circle Trip / Open Jaw Princing Unit whcih is combined with (an) other self-contained One Way / Round Trip / Circle Trip / Open Jaw Pricing Units(s) on the same ticket, e.g. one complete journey divided into separately priced subjourneys.
TC Member	A Member of IATA who has elected to participate in Tariff Coordinating Conferences
Through Fare	A fare applicable for travel between two consecutive fare construction points via an intermediate point(s)
Ticketed Point Mileage (TPM)	The distance between pairs of points published in the Ticketed Point Mileage Manual using non-stop sector mileages in accordance with RESO 011, Ticketed point mileage. The shortest operated mileage between ticketed points.
Ticketed Point	Points shown in the "good for passage" section of the passenger ticket.
Transfer	A change from the service of one carrier to another service of the same carrier (online transfer) or to the service of another carrier (interline transfer)
Trip Origin	First point in the fare component.

Unit Destination	The ultimate stopping place of a pricing unit
Unit Origin	The initial starting point of a pricing unit
USA	The 50 States, District of Columbia, Puerto Rico and US Virgin Islands
USA Teritories	The overseas teritories of the United States of America, including but not limited to · American Samoa, Baker Island, Guam, Howland Island, Jarvis Island · Jonston Atoll, Kingman Reef, Midway Island, Northern Mariana Islands · Saipan, Swains Islands, Pacific Trust Territories, Palmyra Island · Panama Canal Zone, Wake Island
Validated	Fare which has passed rules and routings
VIA points	All ticketed points between the board and off point of a trip.
Western Africa	· Angola, Benin, Burkina Faso, Cameroon, Cape Verde · Central African Republic, Chad, Congo, Cote d’ lovoire · Equatorial Guinea, Gabon, Gambia, Ghana, Guinea, Guinea Bissau · Liberia, Mali, Mauritania, Niger, Nigeria, Sao Tome & Principe · Senegal, Sierra Leone, Togo, Zaire

What is serialization? Does the .NET Framework have in-built support for serialization?

2009-12-29T16:36:42.282125+05:30

Serialization is the process of converting an object into a stream of bytes. Deserialization is the opposite process of creating an object from a stream of bytes. Serialization/Deserialization is mostly used to transport objects (e.g. during remoting), or to persist objects (e.g. to a file or database).

There are two separate mechanisms provided by the .NET class library - XmlSerializer and SoapFormatter/BinaryFormatter. Microsoft uses XmlSerializer for Web Services, and uses SoapFormatter/BinaryFormatter for remoting. Both are available for use in your own code.

What is an Application Domain?

2009-12-29T16:35:06.188375+05:30

An AppDomain can be thought of as a lightweight process. Multiple AppDomains can exist inside a Win32 process. The primary purpose of the AppDomain is to isolate an application from other applications.

Win32 processes provide isolation by having distinct memory address spaces. This is effective, but it is expensive and doesn't scale well. The .NET runtime enforces AppDomain isolation by keeping control over the use of memory - all memory in the AppDomain is managed by the .NET runtime, so the runtime can ensure that AppDomains do not access each other's memory.

.NET Remoting versus Web Services

2009-12-29T14:58:24.67275+05:30

ASP.NET based Web services can only be accessed over HTTP. .NET Remoting can be used across any protocol.
Web services work in a stateless environment where each request results in a new object created to service the request. .NET Remoting supports state management options and can correlate multiple calls from the same client and support callbacks.
Web services serialize objects through XML contained in the SOAP messages and can thus only handle items that can be fully expressed in XML. .NET Remoting relies on the existence of the common language runtime assemblies that contain information about data types. This limits the information that must be passed about an object and allows objects to be passed by value or by reference.
Web services support interoperability across platforms and are good for heterogeneous environments. .NET Remoting requires the clients be built using .NET, or another framework that supports .NET Remoting, which means a homogeneous environment.

How you decide when Not to Use Threads in programming?

2009-12-29T10:03:30.094625+05:30

Multithreading also comes with disadvantages. The biggest is that it can lead to vastly more complex programs. Having multiple threads does not in itself create complexity; it's the interaction between the threads that creates complexity. This applies whether or not the interaction is intentional, and can result long development cycles, as well as an ongoing susceptibility to intermittent and non-reproducable bugs. For this reason, it pays to keep such interaction in a multi-threaded design simple – or not use multithreading at all – unless you have a peculiar penchant for re-writing and debugging!

Multithreading also comes with a resource and CPU cost in allocating and switching threads if used excessively. In particular, when heavy disk I/O is involved, it can be faster to have just one or two workers thread performing tasks in sequence, rather than having a multitude of threads each executing a task at the same time. Later we describe how to implement a Producer/Consumer queue, which provides just this functionality.

Difference between Threads vs. Processes?

2009-12-29T09:26:31.719625+05:30

All threads within a single application are logically contained within a process – the operating system unit in which an application runs.

Threads have certain similarities to processes – for instance, processes are typically time-sliced with other processes running on the computer in much the same way as threads within a single C# application. The key difference is that processes are fully isolated from each other; threads share (heap) memory with other threads running in the same application. This is what makes threads useful: one thread can be fetching data in the background, while another thread is
displaying the data as it arrives.

How the Threading works in .net

2009-12-29T09:25:04.04775+05:30

Multithreading is managed internally by a thread scheduler, a function the CLR typically delegates to the operating system. A thread scheduler ensures all active threads are allocated appropriate execution time, and that threads that are waiting or blocked – for instance – on an exclusive lock, or on user input – do not consume CPU time.

On a single-processor computer, a thread scheduler performs time-slicing – rapidly switching execution between each of the active threads.

On a multi-processor computer, multithreading is implemented with a mixture of time-slicing and genuine concurrency – where different threads run code simultaneously on different CPUs. It's almost certain there will still be some time-slicing, because of the operating system's need to service its own threads – as well as those of other applications.

A thread is said to be preempted when its execution is interrupted due to an external factor such as time-slicing. In most situations, a thread has no control over when and where it's preempted.

One Sentence summary of the purpose of the UML Model

2009-12-28T17:59:30.391+05:30

One Sentence summary of the purpose of the UML Model:

1. Use Cases - "How will our system interact with the outside world?"
2. Class Diagram - "What objects do we need? How will they be related?"
3. Collaboration Diagram - "How will the object interact?"
4. Sequence Diagram - "How will the objects interact?"
5. State Diagram - "What stats should our objects be in?"
6. Package Diagram -"Show are we going to modularise our development?"
7. Component Diagram -"How will our software components be related?"
8. Deployment Diagram -"How will the software be deployed?"