<?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>Untangling The Web &#187; FTP</title>
	<atom:link href="http://www.untanglingtheweb.org/tag/ftp/feed" rel="self" type="application/rss+xml" />
	<link>http://www.untanglingtheweb.org</link>
	<description>Training Small Business Owners How To Use The Internet</description>
	<lastBuildDate>Fri, 11 Nov 2011 21:58:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>How to explain &quot;URLs&quot; so anybody can understand them &#8211; easyDNS Blog</title>
		<link>http://www.untanglingtheweb.org/2008/10/28/how-to-explain-urls-so-anybody-can-understand-them-easydns-blog.html</link>
		<comments>http://www.untanglingtheweb.org/2008/10/28/how-to-explain-urls-so-anybody-can-understand-them-easydns-blog.html#comments</comments>
		<pubDate>Tue, 28 Oct 2008 17:58:32 +0000</pubDate>
		<dc:creator>Conrad Walton</dc:creator>
				<category><![CDATA[web site build]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[domain]]></category>
		<category><![CDATA[FTP]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[web host]]></category>

		<guid isPermaLink="false">http://www.waltonwebdesigner.com/?p=141</guid>
		<description><![CDATA[How to explain &#8220;URLs&#8221; so anybody can understand them &#8211; easyDNS Blog One of our tech support guys just had a conversation with somebody who wanted &#8220;to register the URL http://example.com/something.html&#8221;, where example.com was already registered, the person couldn&#8217;t understand &#8230; <a href="http://www.untanglingtheweb.org/2008/10/28/how-to-explain-urls-so-anybody-can-understand-them-easydns-blog.html">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<blockquote><p><a href="http://blog.easydns.org/archives/236-How-to-explain-URLs-so-anybody-can-understand-them.html" target=newwindow >How to explain &#8220;URLs&#8221; so anybody can understand them &#8211; easyDNS Blog</a></p>
<p>One of our tech support guys just had a conversation with somebody who wanted &#8220;to register the URL http://example.com/something.html&#8221;, where example.com was already registered, the person couldn&#8217;t understand why he couldn&#8217;t have that URL with &#8220;something.html&#8221; after it.</p>
<p>We&#8217;ve heard variations of this one a lot. Like somebody who knows &#8220;xyz.zz&#8221; is taken &#8220;but can I register &#8220;www.xyz.zz?&#8221;, no, you can&#8217;t.</p>
<p>The easiest way to explain a URL such as this one: http://www.example.com/something.html</p>
<p>Is to think of it as HOW, then WHERE and finally WHAT:</p>
<table border="0" cellpadding="4">
<tr>
<td>http://</td>
<td>« how?</td>
<td>The method we are going to use to retrieve or &#8220;get to&#8221; the document described by the URL. Common ones are &#8220;http&#8221; (Hyper-Text Transfer Protocol), you may also see &#8220;ftp://&#8221; or &#8220;mailto:&#8221;</td>
</tr>
<tr>
<td>www.example.com</td>
<td>« where?</td>
<td>This is the hostname of the server, somewhere on the internet, which is holding the document we actually want</td>
</tr>
<tr>
<td>/something.html</td>
<td>« what?</td>
<td>Finally, after we know what server we are looking for and how we&#8217;re going to retrieve the document from it, we now specify exactly which document we want off of the remote server.</td>
</tr>
</table>
<p>Understand those three components and you basically have URLs down cold.</p>
<p>Your web browser (firefox, safari, IE, Opera) is all about &#8220;how&#8221;, what protocols to use to pull all these documents over the web to your desktop.</p>
<p>The web host is the &#8220;what&#8221; machine. It sits on a server and serves document after document to remote web browsers who send it requests.</p>
<p>Something has to bridge the browser to the web host/server and that&#8217;s the &#8220;where&#8221;, that&#8217;s where DNS and domains come in, and that&#8217;s primarily what we do here at easyDNS. We tell web browsers (and other client applications) the &#8220;where&#8221; aspect of retrieving and transmitting documents (the &#8220;whats&#8221;) across the internet. We do this via &#8220;DNS lookups&#8221; &#8230;about a quarter billion times a day.</p>
</blockquote>
<p>Read the entire article at <a href="http://blog.easydns.org/archives/236-How-to-explain-URLs-so-anybody-can-understand-them.html" target=newwindow > How to explain &#8220;URLs&#8221; so anybody can understand them &#8211; easyDNS Blog</a>
<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.untanglingtheweb.org%2F2008%2F10%2F28%2Fhow-to-explain-urls-so-anybody-can-understand-them-easydns-blog.html"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.untanglingtheweb.org%2F2008%2F10%2F28%2Fhow-to-explain-urls-so-anybody-can-understand-them-easydns-blog.html&amp;source=conradwalton&amp;style=normal&amp;service=bit.ly&amp;service_api=R_31989b0d7fed1b2ca61c6228193c1052&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content:encoded>
			<wfw:commentRss>http://www.untanglingtheweb.org/2008/10/28/how-to-explain-urls-so-anybody-can-understand-them-easydns-blog.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

