Image
EAN-139780762782642   EAN-13 barcode 9780762782642
Product NameAncient And Medieval Siege Weapons: A Fully Illustrated Guide To Siege Weapons And Tactics
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHeight:0.9 inches / Length:9.1 inches / Weight:1.6 pounds / Width:7.4 inches
Amazon.comA Buy on Amazon ~ 0762782641
SKU228775856857803746655713
Price New13.34 US Dollars    (curriencies)
Price Used12.87 US Dollars    (curriencies)
Width0.9 inches    (convert)
Height9.1 inches    (convert)
Length7.4 inches    (convert)
Weight25.6 ounces    (convert)
AuthorKonstantin Nossov
Page Count320
BindingPaperback
Published09/04/2012
FeaturesUsed Book in Good Condition
Long DescriptionIn this richly illustrated guide, author Konstantin Nossov masterfully analyzes and recreates the weaponry, tactics, and stratagems of the ancient world. He offers first a comprehensive history of siege warfare in Ancient Egypt, Assyria, Judea, Persia, Greece, and Rome as well as Gaul, the Byzantine Empire, the Muslim world, and Medieval Europe. Discover, among other weapons, how scaling ladders, battering rams, borers, siege towers, throwing machines, and finally cannons developed over time. Numerous charts, illustrations, photographs, and tables explain how engineers constructed and adjusted these weapons and how warriors employed them on the battlefield. Chapters on methods of attack and defense show the weapons in action and reveal the various strategies used to implement and to overcome them. Based on an in-depth analysis of the work of ancient engineers, historians, and generals—including Apollodorus, Herodotus, Julius Caesar, Leonardo da Vinci, Livy, Plutarch, Thucydides, Vitruvius, and others— Ancient and Medieval Siege Weapons not only shows you how to recreate the siege weapons themselves but provides a deeper, clearer picture of the history of war.
Similar Items9780312541408: Castles: A History Of Fortified Structures: Ancient, Medieval & Modern
9781556525261: The Art Of The Catapult: Build Greek Ballistae, Roman Onagers, English Trebuchets, And More Ancient Artillery
9780850459470: Medieval Siege Warfare (Elite)
9780912568188: Castles: Their Construction And History (Dover Architecture)
9780794501440: Castles: Their Construction And History (Dover Architecture)
9780715638910: Castles: Their Construction And History (Dover Architecture)
9780486248981: Castles: Their Construction And History (Dover Architecture)
9780306813580: The Medieval Fortress: Castles, Forts, And Walled Cities Of The Middle Ages
9781841764597: Medieval Siege Weapons (2): Byzantium, the Islamic World & India AD 476–1526 (New Vanguard)
9780826478863: The Medieval Fortress: Castles, Forts, And Walled Cities Of The Middle Ages
View 23 more similar items
Created03-04-2013 12:00:36pm
Modified05-01-2020 1:06:45am
MD5038f926db0db2510f94605aa78038a2b
SHA256c13d3562d3eec8a0982ec2bf7d3384cbc559001bca21293808b0edbf0114e081
Search Googleby EAN or by Title
Query Time0.0260191

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