Image
EAN-130786936264524   EAN-13 barcode 0786936264524
UPC-A786936264524   UPC-A barcode 786936264524
Product NameTarzan
CategoryElectronics / Photography: A/V Media: Movie
Short DescriptionWeight:0.25 pounds
Amazon.comA Buy on Amazon ~ B000AAF1TU
Model2259941
Price New7.50 US Dollars    (curriencies)
Price Used1.51 US Dollars    (curriencies)
RatingG - General Audiences
IMDbIMDb Link
Run Time88 minutes
Aspect Ratio1.66:1
CastBrian Blessed, Glenn Close, Minnie Driver, Nigel Hawthorne, Tony Goldwyn
GenreChildren's
Run Time88 minutes
Width5.5 inches    (convert)
Height0.5 inches    (convert)
Length7.5 inches    (convert)
Weight25 hundredths pounds    (convert)
BindingDVD
FormatDolby, Digital Sound, Surround Sound, NTSC
Published02/13/2015
Run Time88 minutes
FeaturesDisney Tarzan - Special Edition DVD
Long DescriptionSwing into action and adventure with Disney's original classic, TARZAN(R), packed with fun-filled bonus features and award-winning music such as the memorable "You'll Be In My Heart" and "Trashin' The Camp." Disney's magnificent animated adaptation of Edgar Rice Burroughs's story of the ape man begins deep within the jungle when baby Tarzan is adopted by a family of gorillas. Even though he is shunned as a "hairless wonder" by their leader, Tarzan is accepted by the gorillas and raised as one of their own. Together with his wisecracking ape buddy Terk and neurotic elephant pal Tantor, Tarzan learns how to "surf" and swing through the trees and survive in the animal kingdom. His "Two Worlds" collide with the arrival of humans, forcing Tarzan to choose between a "civilized" life with the beautiful Jane and the life he knows and loves with his gorilla family. Filled with humor, heart, and hilarious fun, TARZAN(R) is an unforgettable adventure you'll watch again and again.~~TARZAN(R) Owned by Edgar Rice Burroughs, Inc. And Used by Permission. TARZAN (C) Edgar Rice Burroughs, Inc. and Disney Enterprises, Inc. All Rights Reserved.|With 47 previous movie adaptations, TARZAN(R) is said to be the second most-filmed subject in Hollywood history (topped only by DRACULA) and one of the all-time most popular with moviegoers.|To help prepare them for the film, the directors and a group of artistic supervisors set out on an African safari in March 1996, touring the animal reserves in Kenya, visiting the mountain gorillas in Uganda, and observing Bwindi's Impenetrable Forest.|The city of Tarzana is named after "Tarzan" author Edgar Rice Burroughs' 550-acre Tarzana Ranch, which he later sold to housing developers.|Reportedly, Burroughs was never satisfied with the various screen versions of his book, but according his grandson Danton Burroughs, the Disney version would have pleased his grandfather.
Similar Items3459379402149: A Bug's Life
3459370500516: Toy Story 1 & 2
3459370470833: Hercules
3459370470819: Le Bossu De Notre Dame (The Hunchback Of Notre Dame)
3459370441901: The Aristocats
0786936820591: Aristocats
0786936766776: Mulan/Mulan II
0786936736366: Ratatouille
0786936217896: A Bug's Life
0097361248240: Shrek 2 (Full Screen) / Shrek 3D - Party in the Swamp
View 49 more similar items
Created07-01-2006
Modified05-04-2019 4:35:42pm
MD57f5fe3c8f39977cadbfc9a5e3d2970ad
SHA2569e7cf5bab7bc8beb0de3070b78bd36bf62b3937ad6a1cf1d1761441e2c050cbf
Search Googleby EAN or by Title
Query Time0.0215359

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