Syed1.
BANNED
- Joined
- Dec 7, 2016
- Messages
- 6,306
- Reaction score
- -1
- Country
- Location
Well explained. I however would like to point out that providing API is purely upto the discretion of the vendor.My dear friend, I have worked as a driver developer for the whole 5 years. If what you said is true, then I guess there is no issue of making the radar and EW talk because every device with a driver also provides an API for the client for further integration in his/her system. So the PAF can ask for API from both Radar (china) and EW (Spain) and hire some software developer to make them talk and develop a unified interface for the pilot. Note that I have developed Drivers for many devices like scanners/ printers etc and we are also further asked to develop an API that can be used by the end client as a black-box having all the functions call available to the end-user for integration.
Note that I don't know the technical details of EW or Radar. I have just answered your questions which seem related to my experience. Thanks
Using your printer example I as a vendor could use the same driver for a buyer who pays me $500 for a printer and provide them with API for black and white printing and a buyer who pays me $1000 for b/w and colored printing.
I suppose in military hardware every vendor wants you to use their own proprietary suite of hardware and therefore there is less inclination to provide APIs for integration with other subsystems.
Situation used to be the same with computing hardware in the 70-80s when if you buy an IBM computer you had to buy IBM peripherals. Now if a company does that it'll quickly go out of business.
(Embedded software engineer)