Image
EAN-139780199683758   EAN-13 barcode 9780199683758
Product NameThe Oxford Illustrated History of Modern China
CategoryBook / Magazine / Publication
Amazon.comA Buy on Amazon ~ 0199683751
Price New20.05 US Dollars    (curriencies)
Price Used17.36 US Dollars    (curriencies)
Width0.9 inches    (convert)
Height7.7 inches    (convert)
Length9.7 inches    (convert)
Page Count448
BindingHardcover
Published09/01/2016
FeaturesOxford University Press
Long DescriptionThis lavishly illustrated volume explores the history of China during a period of dramatic shifts and surprising transformations, from the founding of the Qing Dynasty (1644-1912) through to the present day.

The Oxford Illustrated History of Modern China promises to be essential reading for anyone who wants to understand this rising superpower on the verge of what promises to be the "Chinese century", introducing readers to important but often overlooked events in China's past, such as the bloody Taiping Civil War (1850-1864), which had a death toll far higher than the roughly contemporaneous American Civil War. It also helps readers see more familiar landmarks in Chinese history in new ways, such as the Opium War (1839-1842), the Boxer Uprising of 1900, the rise to power of the Chinese Communist Party in 1949, and the Tiananmen protests and Beijing Massacre of 1989.

This is one of the first major efforts to come to terms with the broad sweep of modern Chinese history, taking readers from the origins of modern China right up through the dramatic events of the last few years (the Beijing Games, the financial crisis, and China's rise to global economic pre-eminence) which have so fundamentally altered Western views of China and China's place in the world.
Similar Items9781442208964: Demystifying China: New Understandings Of Chinese History
9781142965846: The Man Awakened From Dreams: One Man’s Life In A North China Village, 1857-1942
9780804750691: The Man Awakened from Dreams: One Man's Life in a North China Village, 1857-1942
9780773428157: The Man Awakened from Dreams: One Man's Life in a North China Village, 1857-1942
9780544334502: Forgotten Ally: China's World War II, 1937-1945
9780520259317: Chen Village: Revolution To Globalization
9780415514996: War And Nationalism In China: 1925-1945 (Routledge Studies In The Modern History Of Asia)
9780393934519: The Search For Modern China (Third Edition)
9780140455489: The Real Story Of Ah-Q And Other Tales Of China: The Complete Fiction Of Lu Xun (Penguin Classics)
9780029336809: Fall Of Imperial China (Transformation Of Modern China Series)
Created12-04-2018 3:45:23pm
Modified12-08-2018 3:13:25am
MD552ae5ee5b1622e17f9949cbe2556f57b
SHA2569b790941eb1a8a5ec9f2ab3701bdc681a40d49f6d8d8036558d09758112c927a
Search Googleby EAN or by Title
Query Time0.0037930

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