I received 63 credits on The Sci Fi Sounds Quiz How much of a Sci-Fi geek are you? | |
Take the Sci-Fi Movie Quizdigital camera ratings |
Saturday, December 22, 2007
The Sci Fi Sounds Quiz: Identify sounds from science fiction movies and TV
Sunday, December 9, 2007
Surf the internet as GoogleBot
- Install User Agent addon for Firefox.
- Tools > User Agent Switcher > Options...
Description: Googlebot
User Agent: Googlebot/2.1 ( http://www.googlebot.com/bot.html) - Tools > User Agent Switcher > Googlebot
- Enjoy
I originally got this information from here: http://forums.digitalpoint.com/showthread.php?t=2589
Tuesday, December 4, 2007
How the Internet works (explained with tennis balls)
link: http://www.managednetworks.co.uk/how-the-internet-works.html
How the Internet works (explained with tennis balls)
Isn't it easy to get confused about nameservers, registrars, domain names, ICANN, whois and so forth? The underlying concepts for building a resilient distributed network might not be too tricky, but as soon as you actually start making that network resilient, distributed and public, it can get mighty complicated.
To make it all simple, we have put together a video that explains how navigating to a URL works, behind the scenes.
To make it all even more simple, we've done it with tennis balls. Everyone understands tennis balls.
f you can't be bothered to watch the whole video, here's the basic sequence of events (without the tennis balls, though, so you might want to go watch the vid). If we want to get the homepage for www.google.com:
- First, the PC sends a request to ICANN in order to find the registrar for Google.com.
- The answer comes back that we need to be talking to the server at whois.enom.com
- Behind the scenes, the PC then needs to find out which nameservers can tell where www.google.com is hosted (whois -h whois.enom.com google.com)
- Once the PC discovers that the answer is ns1.google.com (among others) - with an IP address of 216.239.32.10, we can then dig 216.239.32.10 www.google.com to find out which host we should approach for the web page
- The answer is 64.233.187.99 (among others - I think they might do a bit of load-balancing!).
- This means we now have all the information required to send a GET request to that IP address and receive back the information we need to display the page
Subscribe to:
Posts (Atom)