Disable All Advertising
EAN-139780816150410   EAN-13 barcode 9780816150410
Product NameThe Beast: A Decker/Lazarus Novel (Decker/Lazarus Novels)
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHeight:0 inches / Length:0 inches / Weight:1.19 pounds / Width:0 inches
Amazon.comA Buy on Amazon ~ 0062121758
SKU405218093
Price New2.99 US Dollars    (curriencies)
Price Used1.32 US Dollars    (curriencies)
Width1.21 inches    (convert)
Height9 inches    (convert)
Length6 inches    (convert)
Weight19.04 ounces    (convert)
AuthorFaye Kellerman
Page Count384
BindingHardcover
Published08/06/2013
FeaturesUsed Book in Good Condition
Long DescriptionThe professional and the personal intersect in treacherous ways in this compelling and eerie installment in Faye Kellerman's thrilling New York Times bestselling Decker/Lazarus series Throughout his years with the LAPD, Peter Decker has handled a number of tough cases and strange killers. But few of his previous assignments compare to his latest case—the most bizarre of his storied career. When Hobart Penny is found dead in his apartment, the cops think that his pet cat—an adult female tiger—attacked the reclusive elderly billionaire. But it soon becomes clear that the beast that killed the eccentric inventor is all too human. Digging into the victim's life, Decker and his colleagues, Detectives Marge Dunn and Scott Oliver, discover that Penny was an exceptionally peculiar man with exotic tastes, including kinky sex with call girls. Following a trail of clues that leads from a wildlife sanctuary in the San Bernardino Mountains to the wild nightlife of Las Vegas, the LAPD detectives are left juggling too many suspects and too few answers. To break open a case involving the two most primal instincts—sex and murder—Decker wrestles with a difficult choice. Should he turn to a man with expert knowledge of both, Chris Donatti, the dangerous man who also happens to be the father of Decker's foster son, Gabriel Whitman, a boy not without his own problems? As their work and intimate worlds collide, Decker and his wife, Rina, find themselves facing tough questions. It just might be that family crises and work-related responsibilities prove too much for Decker's career. A confluence of ordeals can stress even the most intact of families. And when all these shocking truths comes out, exactly how well will Decker and Rina cope, and survive?
Similar Items9780753164006: Death Angel
9780739478738: Death Angel
9780061979323: Hangman Lp: A Decker/Lazarus Novel (Decker/Lazarus Novels)
9780525953876: Death Angel
9780394425085: Second Honeymoon
9780253329141: 12th Of Never (Women's Murder Club)
9780152570224: 12th Of Never (Women's Murder Club)
9780727870254: Second Honeymoon
9780312370152: Compound Fractures (Dr. Alan Gregory Novels)
9781557100276: The Quality Of Mercy
View 34 more similar items
Created05-27-2012 1:05:00am
Modified05-01-2020 3:16:41am
MD504f55e0b65e42f87dc4beecab080546b
SHA25667feba6ac18440898115535d750b71fb9a22463b90b260f53a4bc4cd72e41716
Search Googleby EAN or by Title
Query Time0.0280919

An article of interest

Making use of the tools we offer

Creating your own UPC / EAN application

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.