Blogging is a very interesting way for sharing your views with other and also you can know other people view point with the help of blogging. There are many methods of doing blogging but two famous ways are WordPress and Blogspot. In this post, I will be discussing about the difference between the two but before that lets have a look that what these things are.

These days’ people take blogging very seriously. If you want to start your own blog then you can choose hosting of various websites spreaded over internet. The most popular of them are Blogspot and WordPress. The main and most important difference between both of them is that Blogspot provide free services but they are surrounded by advertisements but WordPress is a paid tool. There many WordPress services which are provided for free but most of the services are also paid and if you will not include them in your blog then you will miss some important tricks. So for newbie’s both services are more than good enough.

Second major difference between both of them is of JavaScript. With the help of Blogspot you can include third-party scripts in your blog but in WordPress JavaScript is not permitted. In one you will get faster and clearer interface but in another you will get more interactive interface. So it’s totally up to the user to decide which is more important for him.

Both WordPress and Blogspot permits to create private blogs i.e. the blogs which are not visible to common people. Now here the difference is in the option that who can view them. In Blogspot you are limited to only 100 people but in WordPress you have no restriction. You can choose anyone and can also block the people to whom you don’t want to enter your blog.

At last, the WordPress allows password protection facility in your post (another way to limit you can view your post). These features can’t be enjoyed in Blogspot.

In this informative post we will discuss comparison between two main referencing models which uses the concept of protocol layering. These models are

• Open System Interconnection Model (OSI)
• Transport Control Protocol/ Internet Protocol (TCP/IP)

Both of these models are based on different layers. In OSI model these layers are

• Application layer
• Presentation layer
• Session layer
• Transport layer
• Network layer
• Data link layer
• Physical layer

In TCP/IP model only 4 layers are used. Basically these 7 layers are merged to obtain 4 important layers.

• Application layer
• Transport layer
• Internet layer
• Subnet layer

THE LAYERS OF REFERENCING MODEL
The upper layer of OSI reference model include Application Layer, Presentation Layer and session layer. In TCP/IP only Application layer is considered as upper layer.

• Data link/ Physical Vs. Subnet layer:- The main function of Data Link layer is to provides for the control of the physical layer. It also detects and possibly corrects errors which occurs. The main functioning of physical layer is to provide procedural, functional,electrical and mechanical means for activating a physical connection for bit transmission. 

• Network Vs. Internet layer:- unlike all OSI layers, network layer provides both connection oriented and connection less services. In TCP/IP architecture, the internet layer is exclusively connections. 

• Transport layer:- the main function of transport layer is to provide transparent transfer of data from a source end open system to a destination end open system. In OSI, it takes the information which is to be sent and breaks it into various packets which are sent and then reassembled in a complete message by the transport layer. In TCP/IP it defines two standard transport protocols i.e. UDP and TCP. Here UDP implements an unreliable data stream and TCP implements reliable data stream. 

• Session layer:- In OSI model session layer permits both the parties to hold ongoing communications. This is called session across a network. But this functioning is not found in TCP/IP. In TCP/IP its characteristics are provided by the TCP protocol i.e. Transport layer.

• Presentation layer:- Data format information for network communication is handled by Presentation layer. Basically this is done by converting data into a generic format which can be easily understand by both sides. In TCP/IP this functioning is provided by Application layer. Eg. Multipurpose Internet Mail Extension(MIME) and External Data Representation Standard(XRD).

• Application layer:- It is the topmost layer of reference models. It provides a set of interface for applications to obtain access to networked services and access to the kinds of network services which support application directly. In OSI model FTAM, VT, MHS, DS and CMI works and in TCP/IP FTP,SMTP,TELNET, DNS and SNMP works. The notion of an application process is common to both of the approaches for constructing application entities in different.

ISO APPROACH

Servers are those which accept incoming connections from all users. These server systems serve connected users by providing data and many other services via a connected network connection. Servers generally represents shared resources and they also have the ability to maintain multiple connections at any given amount of time. For accomplishing this, servers handle requests concurrently. For this they use threading or multiple processor. But there are some differences in these approaches, but both these techniques accomplish similar tasks of the same user. Lets have a look what’s the difference in both of them.

Threading and Concurrency

Concurrency refers to the ability of a computer system to run multiple instances of code at a time. Basically the programmer implements concurrency in exactly two ways. The first implementation method is through concurrent processes. In this the programmer generally writes code which generated an entire new programming process and occupies its own process ID and space in memory. The second option if via threads. The thread is run inside the process creation. In this the sharing of resources in done for creating the program, but without the overhead of memory usage.

Concurrent Servers

The main job of concurrent server software is to serve data concurrently instead of handling them serially. It simply means that at a time multiple users can use servers and the server programs, handles requests from various users at the same time. For accomplishing this, the server package creates new instances of the server program for every connection. The process named “daemon” generally listen the incoming connections and then create a new server process for every new connection.

Multithreaded Servers

The goal of multithread servers is same as that of concurrent servers, but it also allows concurrent rather than serial connections for server resources. So here instead of creating a new server process for every new connection to the multithread server creates small threads for execution inside the server program. The working of this thread begins when the user makes a new socket connection, and whenever the connection is lost then it return to the main process.

Concurrent Vs. Multithreaded servers

As it is mentioned that both the server do similar tasks, but there is a slight difference in their way of doing it. A concurrent server uses a separate server process for handling every connection and it will never work perfectly as a multithread server. The server must spawn instances of the new server for every connection. Lightweight threads are used by multithread servers because they are very efficient for connection. Users who want to connect with the server for long time period or those who are engaged in heavy data usage must use their own instances as compared to a thread.