|Product Name||Murder at 1600|
|Category||Electronics / Photography: A/V Media: Movie / TV|
|Short Description||Weight:0.25 pounds|
|Amazon.com||Buy on Amazon ~ 0790732149|
|Price New||2.38 US Dollars (curriencies)|
|Price Used||0.99 US Dollars (curriencies)|
|Rating||R - Restricted|
|Trailer||Watch The Trailer|
|Run Time||107 minutes|
|Cast||Wesley Snipes, Diane Lane, Daniel Benzali, Dennis Miller|
|Director||Dwight H. Little|
|Width||5.38 inches (convert)|
|Height||0.6 inches (convert)|
|Length||7.5 inches (convert)|
|Weight||4 ounces (convert)|
|Format||Multiple Formats, Anamorphic, Closed-captioned, Color, Full Screen, Widescreen, NTSC|
|Run Time||107 minutes|
|Features||MURDER AT 1600 (SNAP CASE PACKAGIN MOVIE|
|Long Description||A 25 year old female White House staffer, Carla Town, is murdered in the White House. D.C. homicide detective Regis is assigned to investigate, only to find evidence suppressed by the Secret Service. After suspecting a cover-up, Regis convinces Secret Service Agent Nina Chance to assist in uncovering the truth. The President's son Kyle Neil is a prime suspect, as he was having sex with Carla within an hour of her murder. While the investigation ensues, the President, Jack Neil, is holding meetings with top military personnel regarding North Korea's holding 23 U.S. military personnel hostage. Regis confronts top Secret Service Agent Spikings at his home shortly after Spikings returns with evidence leading to the murder. The home is attacked and Spikings is killed, but Regis makes it out alive with Agent Chance's assistance, and with the evidence tape. White House adviser Jordan presents false evidence to the President that his son killed Carla and forces the President to say he will announce his resignation at 10 p.m. the following day. Regis and Chance break into the White House via underground tunnels, stop the President from resigning, and arrest Jordan for conspiracy to murder. Jordan pulls a gun, injures Agent Chance, and is killed by multiple Secret Service agents. A news briefing states there were false rumors of the President resigning, and also falsely state that Agent Spikings was killed in the gunfire exchange between Jordan and the Secret Service.|
|Similar Items||0097363273479: Drop Zone|
0086162126291: Rising Sun
0085391562528: U.S. Marshals
0043396509559: Art of War
0024543036500: Rising Sun
0014381688221: Money Train
0012569837683: Fugitive / U.S. Marshals
0012569757691: Passenger 57 / Boiling Point
0012236228707: Minus Man
View 17 more similar items
|Search Google||by EAN or by Title|
Article of interest
This is just a general comment to those that might be interested in some technical info about our site and how Google interacts with it.
Their programmers are very curtious when it comes to their spiders and how they interact with various web sites. Apparently, they are sensative to the load that their spiders place on a web server and do a darn good job when it comes to not overloading a server.
Another major search engine is not quite so nice. If you don't tell them to leave you alone, they will hammer the heck out of your site and potentially bring you to your knees.
Over the past vew days, we have been doing a massive system backup to a couple new off-site backup servers. Normally, this process is pretty quick but because these were new servers they required fully syncronization. Well, I forgot to take into account the drain this could place on our server and I let more than one backup run at a time.
This caused our main server to experience a high load for several days. Google detected this load and backed off its crawling process which was very kind of them. The only bad thing is that when Google backed off, our monitoring process (mostly manual at this point) assumed everything was only slightly higher than normal.
Google may be awesome, but it can be frustrating some times too.
This cool and wonderful feature that Google has in place to prevent overloading a server had an unexpected side affect. Because Google thought our site was super busy (which it was) it reduced the number of people it was referring to the site too. DOH!
As we noticed the visitor count slowly drop we got very confused because the system load was still very high. And we noticed Google wasn't visiting as often as usual and then we saw it... The backup process had overloaded the system. Not to the extreme but enough to make Google think there was a problem. We still actually had plenty of bandwidth for real users just not as much for the bots that visit (which we limit when bandwidth is limited).
Anyway, it was a good learning experience and we are now seeing the referrals climb back up and the Google spider is picking up its pace again too.
We had to force a couple other bots (including that othe big search engine) to play nice because they were trying to take more than their share of our data.
All in all, Google is AWESOME and very powerful. So THANKS GOOGLE for playing nice with others!