Disable All Advertising
Image
EAN-130028485160132   EAN-13 barcode 0028485160132
UPC-A028485160132   UPC-A barcode 028485160132
Product NameDirty Dancing
CategoryElectronics / Photography: A/V Media: Music
Short DescriptionVhs
Amazon.comA Buy on Amazon ~ 6300263673
Price New1.00 US Dollars    (curriencies)
Price Used0.01 US Dollars    (curriencies)
Long DescriptionAs with Grease (1978) and Footloose (1984) before it, Dirty Dancing was a cultural phenomenon that now plays more like camp. That very campiness, though, is part of its biggest charm. And if the dancing in the movie doesn't seem particularly ''dirty'' by today's standards--or 1987's--it does take place in an era (the early '60s) when it would have. Frances ''Baby'' Houseman (Jennifer Grey, daughter of ageless hoofer Joel Grey) has been vacationing in the Catskills with her family for many years. Uneventfully. One summer, she falls under the sway (as it were) of dance instructor Johnny Castle (Patrick Swayze). Baby is a pampered pup, but Johnny is a man of the world. Baby's father, Jake ( Law and Order 's Jerry Orbach), can't see the basic decency in greaser Johnny that she can. It should come as no surprise to find that Baby, who can be as immature as her name, learns more about love and life--and dancing--from free-spirited Johnny than traditionalist Jake. Dirty Dancing spawned two successful soundtracks, a short-lived TV series, and a stage musical. It may be predictable, but Grey and Swayze have chemistry, charisma, and all the right moves. It's a sometimes silly movie with occasionally mind-boggling dialogue--''No one puts Baby in a corner!''--that nonetheless carries an underlying message about tolerance and is filled with the kind of exuberant spirit that's hard for even the most cynical to resist. Not that they'd ever admit it. --Kathleen C. Fennessy
Similar Items9786304990872: Grease [VHS]
9786304117316: Speed
9786303257846: Speed [VHS]
9786302936384: Sleepless in Seattle [VHS]
9786301796538: Pretty Woman [VHS]
9786300214545: Top Gun [VHS]
9786300214378: Footloose [VHS]
9786300184039: Breakfast Club [VHS]
9786300182479: The Day of the Jackal
9781558900271: Pretty Woman [VHS]
9781557229960: Driving Miss Daisy [Vhs]
9780800138073: The Karate Kid [VHS]
9780800131630: The Natural [VHS]
9780800125998: In The Line Of Fire [Vhs]
9780800122676: The Karate Kid [VHS]
9780800121600: A River Runs Through It [VHS]
9780792834977: Road House [VHS]
5050070002935: When Harry Met Sally... [Vhs]
5014781174824: The Lost Boys [VHS]
0717951027030: Speed [Vhs]
Created07-01-2006
Modified04-28-2020 5:01:52pm
MD5da5b4b345c0cc3528f5366727a8696cd
SHA2564aa8398d6383ec3793e00e2b1237c62555dc89d62b982b544a746b3e9e3f92a1
Search Googleby EAN or by Title
Query Time0.0493259

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