Image
EAN-139780762444007   EAN-13 barcode 9780762444007
Product NameThe Rotation: A Season With The Phillies And The Greatest Pitching Staff Ever Assembled
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHeight:8.9 inches / Length:5.98 inches / Weight:0.8 pounds / Width:0.71 inches
Amazon.comA Buy on Amazon ~ 0762444002
SKU749780762444007
Price New6.68 US Dollars    (curriencies)
Price Used2.00 US Dollars    (curriencies)
Width6 inches    (convert)
Height0.7 inches    (convert)
Length8.9 inches    (convert)
Weight12.8 ounces    (convert)
AuthorJim Salisbury, Todd Zolecki
Page Count256
BindingPaperback
Published03/06/2012
Long DescriptionNot since 1957 has one major league team's pitching staff boasted three pitchers (Roy Halladay, Cliff Lee, and Roy Oswalt) in the Top Ten in career winning-percentage. Plus, the Philadelphia Phillies' 2011 rotation also happens to include Cole Hamels—the 2008 NLCS and World Series MVP—and an alternating fifth starter. This awe-inducing rotation has been the talk of baseball since coming together in December 2010. They were featured on the cover of Sports Illustrated's 2011 baseball- preview edition, interviewed on the MLB Network on opening day of spring training, covered in the New York Times Magazine , and mentioned in numerous newspapers and magazines nationwide. Authored by two of the most knowledgable and connected Phillies beat writers, The Rotation is a remarkably detailed day-in-the-life story of one complete season with a Major League Baseball starting-pitching staff. The authors offer deep daily access to the Phillies players, coaches, and front-office staff, as well as the players and staff of other major league teams and the national baseball media. With firsthand reporting and extensive interviews, plus two full-color photo inserts, this is a fascinating and detailed look into the day-to-day operation of what is arguably the greatest pitching rotation ever assembled. It is a must-read for Phillies fans and general baseball fans alike.
Similar Items9780762441105: Harry The K: The Remarkable Life Of Harry Kalas
9781600783180: Mike Schmidt: The Phillies' Legendary Slugger
9781600785344: 162-0: Imagine A Phillies Perfect Season: A Game-By-Game Anaylsis Of The Greatest Wins In Phillies History
9781933822259: Drinking Coffee With A Fork: The Story Of Steve Carlton And The '72 Phillies
9781613210369: Tales From The Philadelphia Phillies Dugout: A Collection Of The Greatest Phillies Stories Ever Told (Tales From The Team)
9780886824556: Tales from the Philadelphia Phillies Dugout: A Collection of the Greatest Phillies Stories Ever Told (Tales from the Team)
9781600786785: 100 Things Phillies Fans Should Know & Do Before They Die (100 Things...Fans Should Know)
9781600786556: Worth The Wait: Tales Of The 2008 Phillies
9781600781643: The Good, The Bad, & The Ugly: Philadelphia Phillies: Heart-Pounding, Jaw-Dropping, And Gut-Wrenching Moments From Philadelphia Phillies History
9780352307392: The Good, The Bad, & The Ugly: Philadelphia Phillies: Heart-Pounding, Jaw-Dropping, And Gut-Wrenching Moments From Philadelphia Phillies History
9781566392310: Phillies '93: An Incredible Season
Created11-22-2012 1:21:14pm
Modified05-01-2020 1:05:34am
MD53e0dcd71b2587fe86f0bfcfa5e239c78
SHA2564100fcf4ec075e0eadad3fbae5604bd8e891d89fe6954c372610a376f946485a
Search Googleby EAN or by Title
Query Time0.0247378

Article of interest

You may have a need for your application to work with our databse. There are many steps in creating an application and the needs of each application can be very different. But the basic data movement contept is pretty much the same in every case.

First of all, your application shouldn't rely on our server. This might seem like a quick way to get your application up and running with little cost but in the end, your app will suffer because it will have to share computing time with every other app that is trying to access our data and network bandwidth. And if we change the way our data is delivered, you would have to re-deploy new copies of your app to every machine.

You should always have your application communicate with your own server. This way you control the format of the communication between your app and the data. And if we need to change our data format, you only need to make the change in the module between your server and our server. Your users running your app won't see any impact or loss of service while changes are made to the communication between your server and our server.

Application Data Diagram

This diagram demonstrates the basic data flow concept. Each device running your application would make requests (red) for data against your server. Your server would talk do your own database to find the needed information and return that information to the requesting devices. When you don't have the data in your database, your server makes a connection to our server requesting the needed information. Our server performs a lookup in our database and if we have the data we return it to your server.

Once you receive the data from our server, you need to store a copy in your database for the next time it is needed by your users. You also need to return the data to the requesting devices just as you would if you found the data in your database in the first place. Except for a slight delay in getting the data, your user shouldn't see any difference beween getting the data directly from your database or getting it from our database.

The odds are, if one user requests a peice of information from your server, another user will request that same information soon after. This is why you need to keep a copy of the data once you query it from our database. You don't want every user to encounter a delay when requesting the same bit of information.

If you are creating your application and database from scratch, there are a few ways to get started. The basic concept that we suggest is the lowest cost and most effective method that we have seen so far. Here are the basic steps you should follow...

 

  1. Create your own database with the information you want to track (few records are needed)
  2. Create your server aplication to control data flow on your system
  3. Create the interface between your server and ours using the data feed process. This can be done for FREE while you are developing. Once you go into production you MAY need to pay a fee to maintain fast data access. But if you feed data back to us you may be able to continue using the free feed. It depends on your actual need.
  4. Build your user application. This can be a phone app or something that is run from computers. Your user app is completly in your control and will talk to your server not ours.
  5. Test your app well. Make sure that when your server can't find the data in your database that it communicates with ours to get the answer.
  6. When your basic testing is done, you should load your database with an initial data load. You can get this data from our download page for a reasonable fee.
  7. Test some more!
  8. Release your app to the world and watch it go.

Althought the details involved in building your application and server and database are going to be different than what others might see, the basic concepts and steps will be similar as outlined here.

We have seen several app developers follow these basic steps with great success. We have also seen a few app developers try to take short cuts only to see their apps fail or strugle.

The key to a successful app is performance and easy maintenance. By creating your own server and keeping your own database you will have control over those aspects. It is much easier to set your application and communication structure up correctly from the start than it is to go back and rebuild it later.

Hopefully, this outline has been of value to you. Take some time to look around the rest of our site, check out our sample data and the data feed pages. Look at our statistics page. And if you still have questions, you are always welcome to ask.

 

Close

Search

Close

Share

Close

Dialog