Image
EAN-130012236114208   EAN-13 barcode 0012236114208
UPC-A012236114208   UPC-A barcode 012236114208
Product NameReservoir Dogs
CategoryElectronics / Photography: A/V Media: Movie / TV
Amazon.comA Buy on Amazon ~ B00005QAOY
Price Used1.38 US Dollars    (curriencies)
IMDbIMDb Link
Aspect Ratio2.35:1
BindingDvd
Long DescriptionQuentin Tarantino came out of nowhere (i.e., a video store in Manhattan Beach, California) and turned Hollywood on its ear in 1992 with his explosive first feature, Reservoir Dogs . Like Tarantino's mainstream breakthrough Pulp Fiction, Reservoir Dogs has an unconventional structure, cleverly shuffling back and forth in time to reveal details about the characters, experienced criminals who know next to nothing about each other. Joe (Lawrence Tierney) has assembled them to pull off a simple heist, and has gruffly assigned them color-coded aliases (Mr. Orange, Mr. Pink, Mr. White) to conceal their identities from being known even to each other. But something has gone wrong, and the plan has blown up in their faces. One by one, the surviving robbers find their way back to their prearranged warehouse hideout. There, they try to piece together the chronology of this bloody fiasco--and to identify the traitor among them who tipped off the police. Pressure mounts, blood flows, accusations and bullets fly. In the combustible atmosphere these men are forced to confront life-and-death questions of trust, loyalty, professionalism, deception, and betrayal. As many critics have observed, it is a movie about ''honor among thieves'' (just as Pulp Fiction is about redemption, and Jackie Brown is about survival). Along with everything else, the movie provides a showcase for a terrific ensemble of actors: Harvey Keitel, Tim Roth, Steve Buscemi, Michael Madsen, Christopher Penn, and Tarantino himself, offering a fervent dissection of Madonna's ''Like a Virgin'' over breakfast. Reservoir Dogs is violent (though the violence is implied rather than explicit), clever, gabby, harrowing, funny, suspenseful, and even--in the end--unexpectedly moving. (Don't forget that ''Super Sounds of the Seventies'' soundtrack, either.) Reservoir Dogs deserves just as much acclaim and attention as its follow-up, Pulp Fiction , would receive two years later.
Similar Items9780792852193: Usual Suspects, The
0883904353485: The Usual Suspects
0796019803885: Grindhouse Presents Death Proof
0031398137689: Jackie Brown
0031398134831: No Country For Old Men
0031398134626: Pulp Fiction
0031398134343: Kill Bill Vol. 1/ Kill Bill Vol. 2 - Double Feature
0027616874818: Usual Suspects, The
0025192014277: Inglourious Basterds
0013132638478: Hateful Eight, The
0013132597256: Django Unchained
Created07-01-2006
Modified04-28-2020 2:38:04pm
MD5bda971dfc8f12ae2b338a3e11383746f
SHA2563652e79c287c023ab33e43f9b29545910afa8992e9e7347d0f4eb4eb0818e309
Search Googleby EAN or by Title
Query Time0.0214510

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