What do You Know About the Internet

[longknife]

Can't find the original site where this appeared but thought it would be fun for all of us on these forums to take. It's @ Unit 1 Web Research Guide Internet Basics Quiz


I missed 2 and 8

 

[Two Thumbs]

missed 2

but really, after free porn, it doesn't really matter

 

[Delta4Embassy]

Know the single most important thing - we're not anonymous.

 

[rightwinger]

Total Question(s): 10
Question(s) Answered: 10
Correct Answer(s): 10

More from my ability to take multiple choice tests than knowledge of the interweb.

 

[Vikrant]

I just looked at that website. It is highly inaccurate in its terminology. For example it defines the World Wide Web as : the part of the Internet that enables information-sharing via interconnected pages. It is wrong and misleading. It is not the pages that are interconnected. It is the networked servers that are interconnected. WWW simply identifies the server as a host of documents that comply with hyper text markup language (HTML) protocol. This enables you to navigate from one page to another by for example clicking a link in the document. When you visit this website, you type -http://www.usmessageboard.com- in your browser. The HTTP portion tells the browser that you are interested in visiting a server which will serve you pages in hyper text markup language. The protocol itself is called hyper text transfer protocol aka HTTP. WWW portion of the URL is basically pointing to a specific canonical machine (CNAME) which is dedicated to serve pages in HTML format. A domain name, in our example case usmessageboard.com may have more than one CNAME. For example: mail.usmessageboard.com for sending and receiving mails. Mail receipt and delivery does not use HTTP protocal. Instead it uses POP or IMAP protocols. So which server (mail or WWW in our example) the request is routed to depends on the protocol identified by sender. If the incoming request is HTTP then the request is routed to -WWW... CNAME. If the request is POP or IMAP, it is routed to mail... CNAME.

In a nutshell, internet can have various transport protocols for exchanging information such as HTTP which is used for WWW compliant documents. It can also use POP3, IMAP, SMTP, MSMQ, FTP and so on.

 

[Uncensored2008]

10 out of 10.

Pretty basic stuff.

 

[Uncensored2008]

I just looked at that website. It is highly inaccurate in its terminology. For example it defines the World Wide Web as : the part of the Internet that enables information-sharing via interconnected pages. It is wrong and misleading. It is not the pages that are interconnected. It is the networked servers that are interconnected. WWW simply identifies the server as a host of documents that comply with hyper text markup language (HTML) protocol. This enables you to navigate from one page to another by for example clicking a link in the document. When you visit this website, you type -http://www.usmessageboard.com- in your browser. The HTTP portion tells the browser that you are interested in visiting a server which will serve you pages in hyper text markup language. The protocol itself is called hyper text transfer protocol aka HTTP. WWW portion of the URL is basically pointing to a specific canonical machine (CNAME) which is dedicated to serve pages in HTML format. A domain name, in our example case usmessageboard.com may have more than one CNAME. For example: mail.usmessageboard.com for sending and receiving mails. Mail receipt and delivery does not use HTTP protocal. Instead it uses POP or IMAP protocols. So which server (mail or WWW in our example) the request is routed to depends on the protocol identified by sender. If the incoming request is HTTP then the request is routed to -WWW... CNAME. If the request is POP or IMAP, it is routed to mail... CNAME.

In a nutshell, internet can have various transport protocols for exchanging information such as HTTP which is used for WWW compliant documents. It can also use POP3, IMAP, SMTP, MSMQ, FTP and so on.

A hypertext LINK is the key concept here. They are interconnected by merit of links.

 

[Vikrant]

I just looked at that website. It is highly inaccurate in its terminology. For example it defines the World Wide Web as : the part of the Internet that enables information-sharing via interconnected pages. It is wrong and misleading. It is not the pages that are interconnected. It is the networked servers that are interconnected. WWW simply identifies the server as a host of documents that comply with hyper text markup language (HTML) protocol. This enables you to navigate from one page to another by for example clicking a link in the document. When you visit this website, you type -http://www.usmessageboard.com- in your browser. The HTTP portion tells the browser that you are interested in visiting a server which will serve you pages in hyper text markup language. The protocol itself is called hyper text transfer protocol aka HTTP. WWW portion of the URL is basically pointing to a specific canonical machine (CNAME) which is dedicated to serve pages in HTML format. A domain name, in our example case usmessageboard.com may have more than one CNAME. For example: mail.usmessageboard.com for sending and receiving mails. Mail receipt and delivery does not use HTTP protocal. Instead it uses POP or IMAP protocols. So which server (mail or WWW in our example) the request is routed to depends on the protocol identified by sender. If the incoming request is HTTP then the request is routed to -WWW... CNAME. If the request is POP or IMAP, it is routed to mail... CNAME.

In a nutshell, internet can have various transport protocols for exchanging information such as HTTP which is used for WWW compliant documents. It can also use POP3, IMAP, SMTP, MSMQ, FTP and so on.

A hypertext LINK is the key concept here. They are interconnected by merit of links.

Hypertext links are part of hypertext markup language which is a specification for creating documents that can have child documents interconnected via hypertext links. The actual navigation (routing) is done by interconnected networks.

 

[Uncensored2008]

Hypertext links are part of hypertext markup language which is a specification for creating documents that can have child documents interconnected via hypertext links. The actual navigation (routing) is done by interconnected networks.

And you believe that means something?

The question specifically spoke of the World Wide Web, not FTP or h.243 protocol. Hypertext creates routable documents by embedding the URL links, allowing reference to resources outside of the hosting domain. These links are absolutely interconnected.

 

[westwall]

I missed number 8

 

[Vikrant]

Hypertext links are part of hypertext markup language which is a specification for creating documents that can have child documents interconnected via hypertext links. The actual navigation (routing) is done by interconnected networks.

And you believe that means something?

The question specifically spoke of the World Wide Web, not FTP or h.243 protocol. Hypertext creates routable documents by embedding the URL links, allowing reference to resources outside of the hosting domain. These links are absolutely interconnected.

The parent document sitting on my server is not interconnected with the child document sitting on your server. Parent document sitting on my server has a reference (link) to the child document sitting on your server. Interconnection implies that there exists a state between duplex connection endpoints. It is absurd to say that an HTML document can do that.

 

[Uncensored2008]

The parent document sitting on my server is not interconnected with the child document sitting on your server. Parent document sitting on my server has a reference (link) to the child document sitting on your server. Interconnection implies that there exists a state between duplex connection endpoints. It is absurd to say that an HTML document can do that.

It implies no such thing.

HTML is not the physical layer.

 

[Vikrant]

The parent document sitting on my server is not interconnected with the child document sitting on your server. Parent document sitting on my server has a reference (link) to the child document sitting on your server. Interconnection implies that there exists a state between duplex connection endpoints. It is absurd to say that an HTML document can do that.

It implies no such thing.

HTML is not the physical layer.

That is the whole point. That is why those documents (HTML) cannot be termed interconnected. That is why the definition given by the website is wrong. However, you supported that definition by not realizing the difference between connection and meta connection.

 

[Asclepias]

I just looked at that website. It is highly inaccurate in its terminology. For example it defines the World Wide Web as : the part of the Internet that enables information-sharing via interconnected pages. It is wrong and misleading. It is not the pages that are interconnected. It is the networked servers that are interconnected. WWW simply identifies the server as a host of documents that comply with hyper text markup language (HTML) protocol. This enables you to navigate from one page to another by for example clicking a link in the document. When you visit this website, you type -http://www.usmessageboard.com- in your browser. The HTTP portion tells the browser that you are interested in visiting a server which will serve you pages in hyper text markup language. The protocol itself is called hyper text transfer protocol aka HTTP. WWW portion of the URL is basically pointing to a specific canonical machine (CNAME) which is dedicated to serve pages in HTML format. A domain name, in our example case usmessageboard.com may have more than one CNAME. For example: mail.usmessageboard.com for sending and receiving mails. Mail receipt and delivery does not use HTTP protocal. Instead it uses POP or IMAP protocols. So which server (mail or WWW in our example) the request is routed to depends on the protocol identified by sender. If the incoming request is HTTP then the request is routed to -WWW... CNAME. If the request is POP or IMAP, it is routed to mail... CNAME.

In a nutshell, internet can have various transport protocols for exchanging information such as HTTP which is used for WWW compliant documents. It can also use POP3, IMAP, SMTP, MSMQ, FTP and so on.

You forgot the most important protocol of them all. The routing protocol that keeps track of where the best routes are to facilitate sending transmissions and replies. The BGP protocol.

 

[Asclepias]

Can't find the original site where this appeared but thought it would be fun for all of us on these forums to take. It's @ Unit 1 Web Research Guide Internet Basics Quiz


I missed 2 and 8

I missed #2 as well. Never even heard of the correct answer.

 

[Vikrant]

Can't find the original site where this appeared but thought it would be fun for all of us on these forums to take. It's @ Unit 1 Web Research Guide Internet Basics Quiz


I missed 2 and 8

I missed #2 as well. Never even heard of the correct answer.

I would not take that site too seriously.

 

[Vikrant]

I just looked at that website. It is highly inaccurate in its terminology. For example it defines the World Wide Web as : the part of the Internet that enables information-sharing via interconnected pages. It is wrong and misleading. It is not the pages that are interconnected. It is the networked servers that are interconnected. WWW simply identifies the server as a host of documents that comply with hyper text markup language (HTML) protocol. This enables you to navigate from one page to another by for example clicking a link in the document. When you visit this website, you type -http://www.usmessageboard.com- in your browser. The HTTP portion tells the browser that you are interested in visiting a server which will serve you pages in hyper text markup language. The protocol itself is called hyper text transfer protocol aka HTTP. WWW portion of the URL is basically pointing to a specific canonical machine (CNAME) which is dedicated to serve pages in HTML format. A domain name, in our example case usmessageboard.com may have more than one CNAME. For example: mail.usmessageboard.com for sending and receiving mails. Mail receipt and delivery does not use HTTP protocal. Instead it uses POP or IMAP protocols. So which server (mail or WWW in our example) the request is routed to depends on the protocol identified by sender. If the incoming request is HTTP then the request is routed to -WWW... CNAME. If the request is POP or IMAP, it is routed to mail... CNAME.

In a nutshell, internet can have various transport protocols for exchanging information such as HTTP which is used for WWW compliant documents. It can also use POP3, IMAP, SMTP, MSMQ, FTP and so on.

You forgot the most important protocol of them all. The routing protocol that keeps track of where the best routes are to facilitate sending transmissions and replies. The BGP protocol.

I specifically kept the routing protocol out of my post to keep it simple and to the point. Because the definition of WWW on that site was wrong so it only warranted discussion of HTTP (Hyper Text Transfer Protocol) to clarify it.