|Product Name||Innocent In Death|
|Category||Book / Magazine / Publication|
|Amazon.com||Buy on Amazon ~ 0749938072|
|Price New||63.83 US Dollars (curriencies)|
|Price Used||1.97 US Dollars (curriencies)|
|Width||0.83 inches (convert)|
|Height||6.97 inches (convert)|
|Length||4.33 inches (convert)|
|Weight||8 ounces (convert)|
|Author||J. D. Robb|
|Long Description||The death of history teacher Craig Foster devastated his young wife, who’d sent him off to work that morning with a lovingly packed lunch. It shocked his colleagues at the Upper West Side private school. And as for the ten-year-old girls who found him in his classroom in a pool of bodily fluids, they may have been traumatized for life.|
Lieutenant Eve Dallas, of course, is more hardened to murder cases. And this is clearly a murder case. That lovingly packed lunch was tainted with deadly ricin. And Mr. Foster’s colleagues, shocked as they may be, have some shocking secrets of their own. It’s Eve’s job to get a feel for all the potential suspects, and find out why someone would have done this to a man who seemed so inoffensive, so pleasant…so innocent.
Now Magdelana Percell – there’s someone Eve can picture as a murder victim. Possibly at Eve’s own hands. The slinky blonde - an old flame of her billionaire husband, Roarke, from his days on the wrong side of the law – has turned up in New York, and she’s anything but innocent. Unfortunately, Roarke seems blind to Magdelana’s manipulation, but not to her shapely figure and flirtatious ways. And he insists that the occasional lunch or business meeting with her is nothing to worry about…and none of Eve’s business. Eve’s so unnerved by the situation that she finds it hard to focus on the Foster case. Still, she’ll have to put aside her anger, jealousy, and heartbreak, for a while at least - because another man has just turned up dead, and the case is taking some strange turns and hitting some frustrating dead ends.
Eve knows all too well that innocence can be a façade. Keeping that in mind may help her solve this case at last. But it may also tear apart her marriage.
|Similar Items||9780425215685: Born In Death|
9780425204184: Survivor In Death
9780425221020: Creation In Death
9780425210734: Memory In Death
9780425204269: Origin In Death
9780425197950: Divided in Death
9780425189030: Portrait In Death
9781594132711: Creation In Death
9781594131721: Memory in Death
9780425226933: Salvation In Death
9780425222898: Strangers In Death
|Search Google||by EAN or by Title|
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!