Discuss the articles posted on Dev.Opera.
By lanej0 
Tuesday, 8. July 2008, 07:08:22
3: How does the Internet work?
This articles explains how the Web works, broadly speaking. It covers the means by which web pages are downloaded from a server into your web browser, and what types of technology are available for creating web pages.
( Read the article )
By lrebrown 
Sunday, 13. July 2008, 14:57:32
Originally posted by lanej0:
http://213.236.208.98 into the address bar and hitting enter—you will get to the same place that you got to in step 1. If you try doing this with http://213.236.208.98 to go to http://dev.opera.com, then it will still go to the same place, but you’ll get a 403 “Access Denied” error—this is because you don’t have permission to access the actual root of this server.
( Read the article )
does that make sense? first you say
http://213.236.208.98 will go to step 1, then you say the same address will go to a 403...
By nberggren Sunday, 13. July 2008, 17:47:35
I realize that this article is supposed to be a quick survey into the topic, but I found very flawed.
The title "How does the world wide web work?" might have been a better choice. While the article does touch upon TCP/IP and DNS, the bulk of the article discusses web pages, leaving out the large number of other protocols that make up the internet. The introduction is at odds with the body of the article. The topics mentioned in the list (presumably because they are important) are barely explained. Meanwhile, a large portion of the words go toward explaining TCP/IP (e.g. IP addresses), yet it isn't even mentioned in the introduction. To represent HTML as the way computers talk to each other is just wrong, and is contradicted later in the server speech bubble, where the HTML is represented as being contained within the HTTP request/response. The "Further Reading" list is just baffling. Rails? PHP? ASP? These are topics for building web pages, not for explaining how the internet (or world wide web) work.
Finally, all the words spent on the hipster first-person attitude clutter what information is present, and act as filler in an underwritten article. I was expecting much better after reading the first article on the history of the internet.
By dorward Sunday, 13. July 2008, 17:49:15
Originally posted by lrebrown:
does that make sense? first you say http://213.236.208.98 will go to step 1, then you say the same address will go to a 403...
No, it doesn't make sense. The request goes to the same server, but not the same place. The root of the the site 213.236.208.98, is different to the root of the site dev.opera.com (and the root of the server is ambiguous enough that it could mean the file system root too).
By chrismills 
Monday, 14. July 2008, 11:16:57
Originally posted by dorward:
I realize that this article is supposed to be a quick survey into the topic, but I found very flawed.
Thanks for the feedback - I've fixed pretty much all of the obvious flaws you list; you've also got to realize that this is for beginners to the world of web development. I'm trying to give them an immediate "quick fix" on the parts of the workings of the internet that will be relevant to them at this stage - this means letting them know in brief how web page addresses work, and what technologies are underlying, and then talking about what technologies they are likely to see being used to create content on the web. To go into a deep discussion of how HTTP and TCP/IP work for example would be pretty much irrelevant to them, and confuse the hell out of them. Let me know if you think my fixes have improved the situation.
Originally posted by dorward:
No, it doesn't make sense. The request goes to the same server, but not the same place. The root of the the site 213.236.208.98, is different to the root of the site dev.opera.com (and the root of the server is ambiguous enough that it could mean the file system root too).
Ah, good catch - I've altered the wording here. Let me know what you think now.
By mpotoka Friday, 10. October 2008, 17:48:50
Why don't any of the images work? I tried at work where there is a filter, but also at home with no firewall/filter and I still cannot see any of the images
By chrismills Monday, 13. October 2008, 21:46:41
Originally posted by mpotoka:
Why don't any of the images work? I tried at work where there is a filter, but also at home with no firewall/filter and I still cannot see any of the image
They display fine for me. Is anyone else having trouble seeing the images?
By stelt Saturday, 31. January 2009, 11:13:38
> retuned
returned
By cx650t Thursday, 11. June 2009, 17:01:09
Originally posted by lanej0:
( Read the article )
http://www.apple.com is basically acting as an alias for http://17.149.160.10/, but why, and how? This is because people are better at remembering words than long strings of numbers. The system that makes this work is called the Domain name system (DNS), which is essentially a comprehensive automatic directory of all of the machines connected to the Internet. When you punch
http://dev.opera.com into your address bar and hit enter, that address is sent off to a name server that tries to associate it to its IP address. There are a ton of machines connected to the Internet, and not every DNS server has a listing for every machine online, so there’s a system in place where your request can get referred on to the right server to fulfill your request.
So the DNS system looks up the www.opera.com web site, finds that it is located at 17.149.160.10, and sends this IP address back to your web browser.
I believe you meant to say www.apple.com as the IP address listed is the same as the first line. Yes?
Or change the referenced IP address to 195.189.143.147 which is what I get when I Ping www.opera.com.
By myakura Monday, 31. August 2009, 03:17:53
Hello.
I just found that the alternative text for Figure 2 wrongly has the same value with Figure 1 ("successful request response cycle").
(Btw I've been working on translating the whole course into Japanese. I expect this one in Japanese is done pretty soon.)
