Image
EAN-139780195147070   EAN-13 barcode 9780195147070
Product NameDivided By Faith: Evangelical Religion And The Problem Of Race In America
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0195147073
SKUACOMMP2_BOOK_USEDGOOD_0195147073
Price New14.27 US Dollars    (curriencies)
Price Used8.00 US Dollars    (curriencies)
Width0.5 inches    (convert)
Height5.1 inches    (convert)
Length7.7 inches    (convert)
Weight5.92 ounces    (convert)
AuthorMichael O. Emerson, Christian Smith
Page Count224
BindingPaperback
Published04/08/2017
Long DescriptionThrough a nationwide telephone survey of 2,000 people and an additional 200 face-to-face interviews, Michael O. Emerson and Christian Smith probed the grassroots of white evangelical America. They found that despite recent efforts by the movement's leaders to address the problem of racial discrimination, evangelicals themselves seem to be preserving America's racial chasm. In fact, most white evangelicals see no systematic discrimination against blacks. But the authors contend that it is not active racism that prevents evangelicals from recognizing ongoing problems in American society. Instead, it is the evangelical movement's emphasis on individualism, free will, and personal relationships that makes invisible the pervasive injustice that perpetuates racial inequality. Most racial problems, the subjects told the authors, can be solved by the repentance and conversion of the sinful individuals at fault.
Combining a substantial body of evidence with sophisticated analysis and interpretation, the authors throw sharp light on the oldest American dilemma. In the end, they conclude that despite the best intentions of evangelical leaders and some positive trends, real racial reconciliation remains far over the horizon.
Similar Items9780195152791: Race: A Theological Account
9780195149197: Race, Nation, And Religion In The Americas
9780195102819: Conjuring Culture: Biblical Formations Of Black America (Religion In America)
9780142001295: Better Day Coming: Blacks And Equality, 1890-2000
9780140082340: Resident Aliens: A Provocative Christian Assessment Of Culture And Ministry For People Who Know That Something Is Wrong
9780070715417: The Black Church in the African American Experience
9780061432958: Mormon America - Revised And Updated Edition: The Power And The Promise
9780060934378: Good And Bad Ways To Think About Religion And Politics
9780029008300: Becoming American?: The Forging Of Arab And Muslim Identity In Pluralist America
9780006367666: A Peculiar People: The Church as Culture in a Post-Christian Society
View 59 more similar items
Created02-26-2012 8:05:44pm
Modified10-06-2017 11:03:29pm
MD52e7a95affffe77b6e0db99889e6c7fa9
SHA2569903471bf56f761be71365da51bae01c70531f4c832f5fffe8f2ee78c6c860e2
Search Googleby EAN or by Title
Query Time0.0301142

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