Diff Between - Http://xyz.. & Http://www.xyz...

[skpanda 0]

hi guyz...

i was sending some link to one of frnds in mail...

https://gen.xyz/....

opend the page immidiately

and

http://forums.xisto.com/no_longer_exists/...

takes ages??!!

can anybody temme the reason behind this!!

[szupie 0]

The www actually has no use in domain names, but it is required if it includes it. The link you gave might have the xyz.com forwarding to the https://xyz.xyz/, so that you have to wait for xyz.com to tell you to go to the www. one, then you will go to the www. one. I'm not sure.

[vujsa 0]

Did you notice that after the page loads, that the address bar shows the www even if you didn't type www?The slow down is caused by the multiple connections to the pages server to figure out what you wanted to see. If you typed the www then there isn't any question and the browser only needs to connect once.vujsa

[skpanda 0]

hmm...i understood...i wonder why is that this delay doesn't happen all the time????

[spacewaste1405241471 0]

Because sometimes people just type the www directly and at those times there r alot more room for extra connections and more processing speed available so it can process ur command faster then if everybody were doing the same thing as u n not including wwwI personaly never include www but thats cuz I can stand 2 w8 a few seconds more

[jipman 0]

an example

xyz.com is a TOP LEVEL domain

www is just a subdomain that links to the TOP level domain

like https://gen.xyz/

I personally think the www subdomain is quite useless.... Since http:// already specifies the protocol, so you don't need www.

[spacewaste1405241471 0]

an example

 

xyz.com is a TOP LEVEL domain

 

www is just a subdomain that links to the TOP level domain

 

like https://gen.xyz/

 

I personally think the www subdomain is quite useless.... Since http:// already specifies the protocol, so you don't need www.

<{POST_SNAPBACK}>

I think the only reason people started using "www" was that when the net was just becoming popular seing www inside the link made it seem cool cuz www stands for world wide web...So people must have been in aww about it...N back then typing http://www.something.com/ was ezer then typing http://forums.xisto.com/no_longer_exists/ cuz back then browsers didn't send you someplace directly if you just typed something.com...You always had to type http:// or www.

[sholomco 0]

i dont know what to tell you but it go's just as fast by mei gues you have a problem whith you browser

[vujsa 0]

The amount of time it takes to load depends on all of the same factors as downloading and uploading files.

Connection Speed (Target Server, Transit Servers, And Client)

Distance Between The Client And Server

Number Of Servers Between The Client And Server

Number Of Analog Lines The Data Travel On

Server Hardware

Client Hardware

Server Load

At a busy time on a busy day if you are using dial-up and have fifteen windows open including a P2P, not typing the www could slow the connection by several seconds.

So I guess it is your decision.

You can be lazy and not type the duba-duba-duba-dot (www.).

-OR-

You can be impatient and press four more keys to load a page faster.

 

Oh by the way, check your bookmarks or favorites and make sure that the entire address is present for each site listed.

 

Happy surfing,

vujsa

[miCRoSCoPiC^eaRthLinG 0]

Okay here's a short explanation as to what might be happening. If you own your own domain and have setup mail/ftp/web services on your server (this is what I faced in linux) - each of those www, ftp, mail etc. actually refer to to individual computers. These names almost function like the netbios names on windows (or in some cases separate services running on the same machine... For example your extremely high load lan might have three different machines catering to mail, ftp and web.. In such a case a typical Domain Name Server configuration file will contain a section like:

..............................
www    10.19.168.1
mail    10.19.168.2
ftp      10.19.168.3
..........
.......

On the other hand, if only ONE machine handles all these functions then the config file might look like..

..............................
www    10.19.168.1
mail    10.19.168.1
ftp      10.19.168.1
..........
.......

Notice that all the names point to the same IP in such a case.

When the routers map an incoming pathway from a remote system to your server, control is handed over to it to redirect the line to an appropriate system on your network, which is able to handle the request. For this, it refers to the local DNS config file containing those records mentioned above to find the right system. When you type:
http://www.mydomain.com/ ----> the server refers to dns config and immediately knows which IP to redirect to..
Similarly for ftp.mydomain.com or mail.mydomain.com ...

When you fail to mention the www part in your URL, the server doesn't know where to send your connection at the first glance. On the second pass - it determines the right system from the protocol (http/ftp/mail) that you've used to fetch the url and only then it can refer to the right system. This process I think causes a slight lag - which you are facing while browsing your urls. Otherwise, whatever speed your connection might be - it should logically take the same amount of time to load the page in each case....

--------------------------------------------------------------
This isn't a Programming Question - moved to Internet Section.
m^e

[qwijibow 0]

I think the reason of this was because in the old days of the internet, nothing about the internet was graphical, it was all command line text based (like command line ftp or telnet)then when web browsers came into use, they decided to add a www. prefix to the graphical stuff so the server could quickly identify what you were viewing its material with.but thats just an educated guess.