Dave Tolls wrote:I'm afraid not.
I picked up most of my stuff through internal projects and the like.
I expect any book I might have used is likely to be outdated by now.
Dave Tolls wrote:The web service is part of the website.
Take www.flybe.com as an example.
If you open up the network tab of your browsers developer tools (in Chrome I right click and select "inspect") and then do a flight search you'll see a bunch of calls to '/api/<something>'.
So your website would do much the same thing, allowing you to write a desktop app that can interact with the site.
You'll find mobile apps that do the same sort of thing, using the exposed web services that were built initially for the associated website.
Stefan Evans wrote:Sounds like you're looking at the right stuff.
Most probably want you want to do is write it in three parts
#1: Web service that stores and manipulates all the information
#2: Website that acts as a front end for the web service so users can enter data easily
#3: Desktop application that connects to the web service to retrieve book information, and can then process the information as it likes.