Image
EAN-135039036011754   EAN-13 barcode 5039036011754
Product NameRoad to Perdition
LanguageEnglish
CategoryElectronics / Photography: A/V Media: Movie / TV
Web Link
Amazon.comA Buy on Amazon ~ B00006FMG0
Model23297DVD
Price New5.04 US Dollars    (curriencies)
Price Used0.98 US Dollars    (curriencies)
RatingR - Restricted
IMDbIMDb Link
TrailerWatch The Trailer
Run Time117 minutes
Aspect Ratio2.35:1
CastJennifer Jason Leigh, Liam Aiken, Rob Maxey, Tom Hanks, Tyler Hoechlin
DirectorSam Mendes
GenreRomance
Run Time117 minutes
Weight15 hundredths pounds    (convert)
BindingDvd
Release Year2002
FormatPAL
Run Time117 minutes
Long DescriptionDirector Nick Love knows how to pick up a poisoned chalice. In choosing to tackle a modern day take on Alan Clarke's 1989 The Firm, he risks the wrath of upsetting those who regard the original so highly, while also being accused of jumping aboard the remake bandwagon. As it turns out, though, he gets away with it all. Love's version of The Firm wisely uses the early film as inspiration rather than a firm template. Thus, while the setting remains underground football violence, Love switches the attention to a different character, the youngster breaking into the crowd. This allows the narrative to focus on his becoming accepted by the group, and then his struggle to break free, which settles into a solid three-act story. It's very much aimed at an adult audience, but that doesn't mean that The Firm is a cheap piece of cinema. Far from it, as it happens. Love's film mixed in sharp violence with sparks of humour, and does so to very good effect. In the process, it sidesteps comparisons to the original by simply going off in a different direction, and works well because of it. It's a little more tempered than some of Nick Love's earlier work too, but perhaps as a consequence, it's also his best film to date.
Similar Items0883929304516: Untouchables
0883929270361: Green Mile
0794043450723: Last Man Standing
0678149167924: Terminal
0085393190927: Once Upon a Time in America
0085391163121: GoodFellas
0031398134565: Gangs Of New York
0025195044912: Public Enemies
0024543215011: Heat
0024543073833: Miller's Crossing
0024543036654: Cast Away
0012569736740: The Departed
0001256973674: The Departed
Created02-19-2016 6:28:21am
Modified04-27-2018 4:38:15am
MD59a02fa4c4f1b9e524dba7b0fe396eafd
SHA256f0ae3f0facecf1caee2fdcb9f2a956e1b5423597a1359d357dfccca340ff2dab
Search Googleby EAN or by Title
Query Time0.0247838

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