<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Learn Software Development &#187; Internet</title>
	<atom:link href="http://learnsoftwareprocesses.com/category/internet/feed/" rel="self" type="application/rss+xml" />
	<link>http://learnsoftwareprocesses.com</link>
	<description>All about the processes involved in software development</description>
	<lastBuildDate>Sun, 20 May 2012 19:17:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Overview Of The Application Layer</title>
		<link>http://learnsoftwareprocesses.com/2009/08/03/overview-of-the-application-layer/</link>
		<comments>http://learnsoftwareprocesses.com/2009/08/03/overview-of-the-application-layer/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 04:41:13 +0000</pubDate>
		<dc:creator>ashish</dc:creator>
				<category><![CDATA[Application Layer]]></category>
		<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Computer networks]]></category>
		<category><![CDATA[The Application layer]]></category>

		<guid isPermaLink="false">http://learnsoftwareprocesses.com/?p=275</guid>
		<description><![CDATA[<p>Computer networks are inherently insecure. To keep information secret, it must be encrypted. Encryption protocols fall into two general classes: secret key (e.g. DES, IDEA), and public key (e.g. RSA). Using these protocols is straight-forward; the hard part is key management. In addition to providing secrecy, cryptographic protocols can also provide authentication. Finally, cryptography can [...]]]></description>
			<content:encoded><![CDATA[<p>Computer networks are inherently insecure. To keep information secret, it must be encrypted. Encryption protocols fall into two general classes: secret key (e.g. DES, IDEA), and public key (e.g. RSA). Using these protocols is straight-forward; the hard part is key management.<br />
In addition to providing secrecy, cryptographic protocols can also provide authentication. Finally, cryptography can also be used to allow messages to be signed in such a way that the sender cannot repudiate them after they have been sent. Naming in the Internet uses a distributed database system, DNS. Domain Name Server(DNS) holds records with IP addresses, mail exchanges, and other information. By querying a DNS server, a process can map an Internet domain name onto the IP address used to communicate with that domain.<br />
As networks grow larger, they become harder to manage. For this reason, special network management systems and protocols have been devised, the most popular of which is SNMP. This protocol allows managers to communicate with agents inside devices to read out their status and issue commands to them.<br />
Four major network applications are electronic mail, USENET news, the World Wide Web, and multimedia. Most email systems use the mail system defined in RFCs 821 and 822. Messages sent in this system use system ASCII headers to define message properties. These messages are sent using SMTP. Two systems for securing email exist, PGP and PEM.<br />
USENET news consists of thousands of newsgroups on all manner of topics. People can join newsgroups locally, and can then post messages all over the world using the NNTP protocol, which has some resemblance to SMTP.<br />
The World Wide Web is a system for linking up hypertext documents. Each document is a page written in HTML, possible with hyperlinks to other documents. A browser can display a document by establishing a TCP connection to its server, asking for the document, and then closing the connection. When a hyperlink is selected by the user, that document can also be fetched in the same way. In this manner, documents all over the world are linked together in a giant web.<br />
Multimedia is the rising star in the networking firmament. It allows audio and video to be digitized and transported electronically for display. Most multimedia projects use the MPEG standards and transmit the data over ATM connections. </p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://learnsoftwareprocesses.com/2009/08/03/overview-of-the-application-layer/' addthis:title='Overview Of The Application Layer '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://learnsoftwareprocesses.com/2009/08/03/overview-of-the-application-layer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Overview Of The Transport Layer</title>
		<link>http://learnsoftwareprocesses.com/2009/08/03/overview-of-the-transport-layer/</link>
		<comments>http://learnsoftwareprocesses.com/2009/08/03/overview-of-the-transport-layer/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 04:34:31 +0000</pubDate>
		<dc:creator>ashish</dc:creator>
				<category><![CDATA[Internet]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Protocols]]></category>
		<category><![CDATA[Transport Layer]]></category>
		<category><![CDATA[ATM]]></category>
		<category><![CDATA[Computer networks]]></category>

		<guid isPermaLink="false">http://learnsoftwareprocesses.com/?p=273</guid>
		<description><![CDATA[<p>The transport layer is the key to understanding layered protocols. It provides various services, the most important of which is an end-to-end, reliable, connection-oriented byte stream from sender to receiver. It is accessed through service primitives that permit the establishment, use and release of connection. Transport protocols must be able to do connection management over [...]]]></description>
			<content:encoded><![CDATA[<p>The transport layer is the key to understanding layered protocols. It provides various services, the most important of which is an end-to-end, reliable, connection-oriented byte stream from sender to receiver. It is accessed through service primitives that permit the establishment, use and release of connection.<br />
Transport protocols must be able to do connection management over unreliable networks. Connection establishment is complicated by the existence of delayed duplicate packets that can reappear at inopportune moments. To deal with them, three-way handshakes are needed to establish connections. Releasing a connection is easier than establishing one, but is still far from trivial due to the two-army problem.<br />
Even when the network layer is completely reliable, the transport layer has plenty of work to do. It must handle all the service primitives, manage connections and timers, and allocate and utilize credits.<br />
The main Internet transport protocol is TCP. It uses a 20-byte header on all segments. Segments can be fragmented by routers within the Internet, so hosts must be prepared to do reassembly. A great deal of work has gone into optimizing TCP performance, using algorithms from Nagle, Clark, Jacobson, Karn and others.<br />
ATM has four protocols in the AAL layer. All of them break messages into cells at the source and reassemble the cells into messages at the destination. The CS and SAR sublayers add their own headers and trailers in various ways, leaving from 44 to 48 bytes of cell payload.<br />
Network performance is typically dominated by protocol and TPDU processing overhead, and the situation gets worse at higher speeds. Protocols should be designed to minimize the number of TPDUs, context switches, and times each TPDU is copied. For gigabit networks, simple protocols using rate, rather than credit, flow control are called for.</p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://learnsoftwareprocesses.com/2009/08/03/overview-of-the-transport-layer/' addthis:title='Overview Of The Transport Layer '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://learnsoftwareprocesses.com/2009/08/03/overview-of-the-transport-layer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quick Tip: URLs &#8211; Uniform Resource Locator</title>
		<link>http://learnsoftwareprocesses.com/2009/07/09/quick-tip-urls-uniform-resource-locator/</link>
		<comments>http://learnsoftwareprocesses.com/2009/07/09/quick-tip-urls-uniform-resource-locator/#comments</comments>
		<pubDate>Thu, 09 Jul 2009 09:21:49 +0000</pubDate>
		<dc:creator>ashish</dc:creator>
				<category><![CDATA[Definition]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[IP address]]></category>
		<category><![CDATA[Protocol]]></category>
		<category><![CDATA[Uniform Resource Locator]]></category>
		<category><![CDATA[URL]]></category>
		<category><![CDATA[Web Applications]]></category>
		<category><![CDATA[Web page]]></category>
		<category><![CDATA[World wide web]]></category>
		<category><![CDATA[WWW]]></category>

		<guid isPermaLink="false">http://learnsoftwareprocesses.com/?p=228</guid>
		<description><![CDATA[<p>URLs, or Uniform Resource Locators, are the method by which documents or data are addressed in the World Wide Web. The URL contains the following information: </p> <p>- the protocol. - the DNS name of the machine on which the page is located. - the local name uniquely indicating the specific page. - the location [...]]]></description>
			<content:encoded><![CDATA[<p>URLs, or Uniform Resource Locators, are the method by which documents or data are addressed in the World Wide Web. The URL contains the following information: </p>
<p>- the protocol.<br />
- the DNS name of the machine on which the page is located.<br />
- the local name uniquely indicating the specific page.<br />
- the location of the resource in the directory structure of the server.</p>
<p>To make a piece of text clickable, the page writer must provide two items of information : the clickable text to be displayed and the URL of the page to go to if the text is selected. Once the text is selected, the browser looks up the host name using DNS. Now armed with the host&#8217;s IP address, the browser establish TCP connection to host. Over that connection, it sends the file name using the specified protocol.<br />
The URL scheme is open to have protocols other than HTTP also. In short, URL&#8217;s have been designed to not only allow users to navigate the Web, but to deal with FTP, news, Gopher, email, and telnet as well, making all the specialized user interface programs for those other services unnecessary, and thus integrating nearly all Internet access into a single program, the Web Browser.<br />
The growing use of the Web has turned up an weakness in URL scheme. A URL points to one specific host. For pages that are heavily referenced, it is desirable to have multiple copies far apart, to reduce network traffic. The advent of systems such as Akami are meant to meet that need, distributing content over multiple servers on a global level. </p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://learnsoftwareprocesses.com/2009/07/09/quick-tip-urls-uniform-resource-locator/' addthis:title='Quick Tip: URLs &#8211; Uniform Resource Locator '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://learnsoftwareprocesses.com/2009/07/09/quick-tip-urls-uniform-resource-locator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WWW &#8211; The Server Side</title>
		<link>http://learnsoftwareprocesses.com/2009/07/06/www-the-server-side/</link>
		<comments>http://learnsoftwareprocesses.com/2009/07/06/www-the-server-side/#comments</comments>
		<pubDate>Mon, 06 Jul 2009 19:20:52 +0000</pubDate>
		<dc:creator>ashish</dc:creator>
				<category><![CDATA[Internet]]></category>
		<category><![CDATA[Browsers]]></category>
		<category><![CDATA[Connection]]></category>
		<category><![CDATA[FTP]]></category>
		<category><![CDATA[Gopher]]></category>
		<category><![CDATA[HTTP]]></category>
		<category><![CDATA[IP address]]></category>
		<category><![CDATA[Protocol]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[TCP]]></category>
		<category><![CDATA[World wide web]]></category>
		<category><![CDATA[WWW]]></category>

		<guid isPermaLink="false">http://learnsoftwareprocesses.com/?p=226</guid>
		<description><![CDATA[<p>For all the incoming connectionts from different clients, every website is associated with a server process listening to TCP port 80. The client sends a request after the connection is made and the server sends the reply and then the connection is released. The protocol that is responsible for requests and replies is called HTTP.</p> [...]]]></description>
			<content:encoded><![CDATA[<p>For all the incoming connectionts from different clients, every website is associated with a server process listening to TCP port 80. The client sends a request after the connection is made and the server sends the reply and then the connection is released. The protocol that is responsible for requests and replies is called HTTP.</p>
<p>The steps that occur between the user clicking and a page being displayed are:<br />
- The browser determines the URL.<br />
- The browser asks DNS for IP address.<br />
- DNS replies.<br />
- Browser makes a TCP connection to the port.<br />
- It then sendsthe GET command.<br />
- The server sends the file.<br />
- The TCP connection is released.<br />
- The browser displays the text of the file.<br />
- The browser fetchesand displays all images of the file.</p>
<p>Not all servers speak HTTP, Old servers use FTP, Gopher or other protocols. Given the number of different protocols, it was thought impractical to make browser understand different protocols. However, since there is a need to make information available (where the server talks in protocols other than HTTP), a solution was required. This solution is something called a proxy server. A proxy server takes a HTTP request from the browser and translates these requests into the FTP/Gopher/other protocols. The proxy server is a separate logical server.<br />
A proxy server also serves to provide an important function called caching. Through caching, a proxy server keeps a local copy of the pages that pass through it. If a user requests for a page, if the page is present on the cache of the proxy server, it serves the page to the user. this way it serves to reduce load on final server.</p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://learnsoftwareprocesses.com/2009/07/06/www-the-server-side/' addthis:title='WWW &#8211; The Server Side '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://learnsoftwareprocesses.com/2009/07/06/www-the-server-side/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introduction: WWW &#8211; The Client Side</title>
		<link>http://learnsoftwareprocesses.com/2009/07/03/introduction-www-the-client-side/</link>
		<comments>http://learnsoftwareprocesses.com/2009/07/03/introduction-www-the-client-side/#comments</comments>
		<pubDate>Fri, 03 Jul 2009 15:04:44 +0000</pubDate>
		<dc:creator>ashish</dc:creator>
				<category><![CDATA[Internet]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Browsers]]></category>
		<category><![CDATA[Client]]></category>
		<category><![CDATA[Hypermedia]]></category>
		<category><![CDATA[Hypertext]]></category>
		<category><![CDATA[Page]]></category>
		<category><![CDATA[Web Applications]]></category>
		<category><![CDATA[World wide web]]></category>
		<category><![CDATA[WWW]]></category>

		<guid isPermaLink="false">http://learnsoftwareprocesses.com/?p=224</guid>
		<description><![CDATA[<p>The Internet / World Wide Web consists of pages and each page contains links or pointers to other pages. Users follow the link by clicking on them. This process can be repeated indefinitely, possibly traversing hundreds of linked pages. Pages that point to other pages are said to use &#8220;hypertext&#8221;.</p> <p>Pages are viewed with a [...]]]></description>
			<content:encoded><![CDATA[<p>The Internet / World Wide Web consists of pages and each page contains links or pointers to other pages. Users follow the link by clicking on them. This process can be repeated indefinitely, possibly traversing hundreds of linked pages. Pages that point to other pages are said to use <span style="font-style:italic;">&#8220;hypertext&#8221;</span>.</p>
<p>Pages are viewed with a program called a <span style="font-style:italic;">browser</span>. When a page is requested, the browser fetches, interprets the text and formats the commands that it contains and displays the page. Strings of text that are links to other pages are called <span style="font-style:italic;">hyperlinks</span>.</p>
<p>Most browsers have numerous buttons and features to navigate the Web. In addition to having ordinary text and hypertext, web pages also contain icons, line drawings, maps and photographs. Some pages also consist of audio tracks, video clips, or both. When hypertext pages are combined with other media, the result is called <span style="font-style:italic;">hypermedia</span>. Many Web pages consists of large images which take a long time to load. </p>
<p>Some browsers deal with slow loading of images by first fetching and displaying the text, then getting the images. Some Web pages contain forms that request the user to enter information. Some browsers use the local disk to cache pages that they have fetched. A check is made before a page is fetched to see if it is in the local cache. If so, check if it is up to date. If so,there is no need to load the page again.</p>
<p>To host a web browser, a machine must be directly connected to Internet or have a SLIP or PPP connection to a router or other machine that is directly on Internet.    </p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://learnsoftwareprocesses.com/2009/07/03/introduction-www-the-client-side/' addthis:title='Introduction: WWW &#8211; The Client Side '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://learnsoftwareprocesses.com/2009/07/03/introduction-www-the-client-side/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

