Image
EAN-135039036027809   EAN-13 barcode 5039036027809
Product NameFantastic Four 1 Disc [Import anglais]
LanguageEnglish
CategoryElectronics / Photography: A/V Media: Movie
Amazon.comA Buy on Amazon ~ B001NDTA8Q
Price New6.09 US Dollars    (curriencies)
Price Used2.98 US Dollars    (curriencies)
CastIoan Gruffudd, Jessica Alba, Chris Evans, Michael Chiklis, Julian McMahon
GenreKIDS & FAMILY
BindingDvd
FormatPAL
Run Time106 unknown-units
Long DescriptionUK Released DVD/Blu-Ray item. It MAY NOT play on regular US DVD/Blu-Ray player. You may need a multi-region US DVD/Blu-Ray player to play this item. Fantastic Four is a light-hearted and funny take on Marvel Comics' first family of superherodom. It begins when down-on-his-luck genius Reed Richards (Ioan Gruffudd) has to enlist the financial and intellectual help of former schoolmate and rival Victor Von Doom (Julian McMahon) in order to pursue outer-space research involving human DNA. Also on the trip are Reed's best friend, Ben Grimm (Michael Chiklis); his former lover, Sue Storm (Jessica Alba), who's now Doom's employee and love interest; and her hotshot-pilot brother, Johnny Storm (Chris Evans). Things don't go as planned, of course, and the quartet becomes blessed--or is it cursed?--with superhuman powers: flexibility, brute strength, invisibility and projecting force fields, and bursting into flame. Meanwhile, Doom himself is undergoing a transformation. Among the many entries in the comic-book-movie frenzy, Fantastic Four is refreshing because it doesn't take itself too seriously. Characterization isn't too deep, and the action is a bit sparse until the final reel (like most "first" superhero movies, it has to go through the "how did we get these powers and what we will do with them?" churn). But it's a good-looking cast, and original comic-book co-creator Stan Lee makes his most significant Marvel-movie cameo yet, in a speaking role as the FF's steadfast postal carrier, Willie Lumpkin. Newcomers to superhero movies might find the idea of a family with flexibility, strength, invisibility, and force fields a retread of The Incredibles, but Pixar's animated film was very much a tribute to the FF and other heroes of the last 40 years. The irony is that while Fantastic Four is an enjoyable B-grade movie, it's the tribute, The Incredibles, that turned out to be a film for the ages. --David Horiuchi, Amazon.com
Similar Items0043396409415: Amazing Spider-Man
0012569823372: Superman Returns
0024543144632: Fantastic Four
0883929140237: Green Lantern (+ Ultraviolet Digital Copy)
0025195020251: Hulk
0043396163119: Ghost Rider
0012236162438: Punisher
0024543077947: Daredevil (Full Screen Edition)
0025195016025: Incredible Hulk
0024543470779: Fantastic Four Rise of the Silver Surfer
0024543182641: Elektra
0024543117315: Daredevil: Director's Cut
Created09-02-2015 10:27:28pm
Modified03-07-2018 4:01:41pm
MD5aceb29fa8cff3fad8f8a643017c9af1e
SHA256a5777259f486fa1a37d16de82af064e3bf113b8c451dfa947205a4fe774ab474
Search Googleby EAN or by Title
Query Time0.0157151

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