|Product Name||Origin Of Haloes|
|Category||Book / Magazine / Publication|
|Amazon.com||Buy on Amazon ~ 077102620X|
|Price New||1.99 US Dollars (curriencies)|
|Price Used||0.01 US Dollars (curriencies)|
|Long Description||When sixteen-year-old gymnast Kay Clancy finds herself pregnant by the handsome Coach Halliwell, she tells a lie that has dire consequences. Despite her transgressions, she manages to marry the young Joe LeBlanc, and embarks on a happy life with him until suddenly, late in Kay’s third pregnancy, he vanishes, along with his treasured canoe. Joe is nowhere to be found, but his paddle surfaces near a dock in front of the Halliwell home, where the coach lives with his manic but fragile wife, Marie, and their son, Eddie. Years on, Margar, the mischievous daughter Joe never knew, is determined to find her father. Time and again she is drawn to that house by the river. What Margar discovers there will change forever the way she views her family.|
From the acclaimed author of Water Wings and The Perpetual Ending, Origin of Haloes is a novel of lives large and small, interweaving captivating vignettes from Olympic history and Greek mythology with small-town Ontario to tell a story of love, betrayal, and loss.
|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!