Yeah, it's 10:00pm on a Saturday night and I'm blogging about hockey. I know my life is lame. But I don't care. Tonight we won. Here are some observations from the game.
*Theodore started in goal again after giving up 4 on 17 shots last night. He did his best to impersonate last night's performance in the first period by giving up a weak goal five hole 26 seconds in. I really wanted to blame the second goal on him too but I convinced myself that he was screened and couldn't see it. As the game progressed he seemed to calm down making all the saves he needed to. Congratulations to him on getting his first win as a Capital.
*The Brashear-Steckel-Bradley was by far the best line on the ice for the Caps through the first two periods. Steckel set up Bradley on a cross goal pass to get the Caps back to 2-1 in the first period providing a much needed spark before the first intermission. The trio was a combined +4 for the game.
*Watching Mike Green all of last season and thru two games this season, he is starting to look more and more like Brian Campbell. They both play the powerplay point and know when to jump into the attack. Both like to carry the puck from one end of the ice to the other kind of acting as a fourth forward. Hopefully Green can start to throw his body around a little more at the blueline like Campbell or dare I say...Scott Stevens.
*Not like I was keeping track or anything but midway through the third I'm pretty sure I heard Joe B. say that Fedorov 7 for 8 on faceoffs. I can't remember us having a guy as consistently productive as Feds since Adam Oates in the late 90's. Having a guy who you know can win any draw in any situation is invaluable, especially late in games and in the playoffs. It was also nice to see him wearing the 'A' on his sweater. He deserves it.
*And finally, as I predicted last night...Alex Ovechkin torched Chicago. Two goals and almost 25 minutes of ice time. As good as Khabibulin was, there was no stopping Ovie tonight. The only thing missing was that Huet wasn't in goal
We're 1-1-0 now. 80 games left and Alex Ovechkin is on pace for 82 goals. Tonight calls for celebratory Stoli. Next game Monday home to Vancouver.
Subscribe to:
Post Comments (Atom)
1 comment:
From http://www.website-awards.net/articles/article39.htm:
Bandwidth stealing is a serious problem, but many webmasters are not aware of this. Some don't even know what it is! This article defines bandwidth stealing and explains how it affects you. After reading this article, you will know why you shouldn't do it, how to avoid doing it, how to detect it, and how to deal with the offenders.
Owners of award programs are in a unique position to combat this problem. We are frequently visiting sites, and there are measures we can take when we come across one that is stealing bandwidth. Learn and apply these measures. By working together, we can all help to overcome the problem.
What Is Bandwidth?
When you surf the Internet or download a file, you are using bandwidth. Every time you click on a link to a Web page, your server sends a message to the remote server where the page is located and requests the page. The remote server, in turn, sends back all the files associated with that page. This transfer of data is called "bandwidth."
What Is Bandwidth Stealing?
You created a website and all the elements associated with that site, such as graphics, HTML files, sounds, and so forth. Under the copyright laws of most countries in the world, they belong to you, the creator. They are your property and nobody is allowed to copy or use them without your permission.
One day, while checking your server logs, you discover that the graphic you created as a link to a resource in your site has been accessed more times than the page it's located on. "How can this be," you wonder. "Shouldn't it be loaded the same number of times as the page?"
Later you're looking through the list of referral sites in your server logs. Out of curiosity, you click on the link to a site that referred the page you were wondering about. There, in the middle of the page, is a copy of your graphic and it's linked to your page. "Isn't that wonderful," you think, forgetting about the copyright issue for the moment. "He's linking to my site."
Still curious, and perhaps a little bit proud, you open and examine the source code for this page. Guess what! The webmaster did not store the graphic on his server. To save his own bandwidth, he has coded the link to call it from your server. This is called "bandwidth stealing."
Post a Comment