|Product Name||The 1964 Phillies: The Story Of Baseball's Most Memorable Collapse|
|Category||Book / Magazine / Publication|
|Amazon.com||Buy on Amazon ~ 0786421177|
|Price New||27.08 US Dollars (curriencies)|
|Price Used||19.95 US Dollars (curriencies)|
|Width||0.45 inches (convert)|
|Height||9 inches (convert)|
|Length||6.34 inches (convert)|
|Weight||9.76 ounces (convert)|
|Author||John P Rossi|
|Features||Used Book in Good Condition|
|Long Description||In 1964, thousands of Philadelphia baseball fans were caught up in the Phillies' unexpected run at the National League pennant. Nearly a decade of continuous defeat had earned them little more than the reputation for an unprecedented record of consecutive losses. But in that '64 season the Phillies shocked the baseball world, taking over the National League in mid-July and holding on to first place for 73 consecutive days. And then, as the team's first pennant in a generation seemed within reach, the Phillies collapsed in the greatest meltdown in baseball history. This account traces the rise and fall of that year's Phillies team and attempts to disentangle the complex issues that ultimately cost them the pennant. The book sheds light on the influential events of the fifties and sixties that rendered the team first futile and then undefeated, beginning with an exploration of Philadelphia itself and its team in the 1950s. Early chapters discuss the acquisition of a new manager (Gene Mauch) and the dramatic additions of a dynamic new pitcher (Jim Bunning) and the first great African American player produced by the farm system (Richie Allen). Following chapters focus specifically on the 1964 season and its critical moments, from Jim Bunning's perfect game and Johnny Callison's winning home run in the All-Star game, to Chico Ruiz's steal of home that began the devastating 10-game losing streak at the end of the season. Final chapters analyze what went wrong during the season and discuss the Phillies' position in baseball today. Three useful appendices provide the statistics for the games of the '64 season and for the individual players on the team, and detailed statistics for the 10-game losing streak.|
|Similar Items||9781935592105: Relive The Philadelphia Eagles 1960 Championship Season|
9781933599519: The Year Of Blue Snow: The 1964 Philadelphia Phillies (Sabr Digital Library) (Volume 12)
9781878282460: The Glory Of The 1966 Orioles And Baltimore
9781600788017: "Then Bowa Said To Schmidt. . .": The Greatest Phillies Stories Ever Told (Best Sports Stories Ever Told)
9781600785344: 162-0: Imagine A Phillies Perfect Season: A Game-By-Game Anaylsis Of The Greatest Wins In Phillies History
9781597974318: A Tale Of Three Cities: The 1962 Baseball Season In New York, Los Angeles, And San Francisco
9781578604630: Before The Machine: The Story Of The 1961 Pennant-Winning Reds
9780786432141: The Amazin' Mets 1962-1969
9780708842553: The Year Of Blue Snow: The 1964 Philadelphia Phillies (Sabr Digital Library) (Volume 12)
9780271027425: September Swoon: Richie Allen, the ’64 Phillies, and Racial Integration (Keystone Books)
|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!