When a client sends a request to a server, an HTTP request is created with a header consisting of information about the user and requested page.

In a similar way, when the server provides the appropriate page back to the client, an HTTP response is generated with a header having information about the document being sent.

In an all, HTTP protocol is used for communicating on the web.

This HTTP protocol is stateless and to make it stateful, we use Cookies and Session.

Difference between Cookies and Session in Tabular form

Session

A session is used to provide stateful communication between client and server. It maintains the state by storing the information at the server side.

It assigns a unique session ID to every user at first visit on the website and the same session id is saved at the client’s machine in the cookies.

Cookie

At the client level, Cookies are the small piece of information which is sent by the server to identify the user and its activities uniquely.

In this method, the information is stored locally on the user’s browser and later on, this information is then being sent to the server whenever the information is needed ( when the user again visits that site).

How do cookies and session work?

When a client’s computer requests a webpage from a server ( a Website), in return, the server answers back with the requested webpage. This is how client/server approach works.

However, it is crucial to keep information about users in order to monitor the behavior carried out by them on various webpages. This can be done by maintaining state.

As it helps in the further development of complex interactive web-based applications.

If a server isn’t capable of maintaining the state then it would forget all the information about a visitor and the page on which he landed on, as and when it responded.

To overcome this problem, this type of information is stored on the server itself or the user’s browser locally. One of the way is cookie and session.

Difference between HTML and XML in Tabular form

HTML

The mark–up language which is used for creating webpages is called HTML. It employs TAGS which help in constructing and presenting the layout of the webpage. All the HTML elements are evaluated and run on the browser and present it over the screen.

XML

The mark – up language which helps the user to calibrate data representation or the structure of data in which each and every detail is assigned. This XML mark–up language can be used to create user-defined tags and user-defined mark–up language. The XML focuses on the fact that how the data is stored.

Key Differences

• FULL FORM

HTML stands for Hypertext mark–up Language; whereas; XML stands for eXtensible mark–up Language.

• GENERAL

HTML language is an already predefined language; whereas; when we talk about the XML language then, the XML language provides a credible framework for defining the mark – up languages.

• STRUCTURAL INFORMATION

In case of the HTML language, this mark – up language does not contain any kind of structural information, whereas; in case of XML language then, this mark – up language always contain the structural information.

• LANGUAGE PURPOSE

When we consider the HTML language, the purpose of this mark–up language is to effectively represent the data; whereas; when we consider the XML language, the purpose of this mark–up language is to have an efficient transfer of information.

• WHITE SPACE PRESERVATION

In the HTML language there is no preservation of the white spaces as such; whereas; when we talk about the XML language then, in the XML language the white spaces can be preserved.

• CLOSING TAGS

In case of the HTML language, it has an optional approach towards them as, some tags can also work without closing tags; whereas; in case of the XML language, it has a compulsory approach towards them as every tag is required to have a closing tag.

• NESTING

When we consider the HTML language then, the nesting has no valuable effect on the HTML code, so there is no need for it; whereas; when we consider the XML language then, the nesting has a great value in the XML code, so it must be properly done.