Pragmatically our experimental system will be composed of a few subsystems. As our requirements specify to be able to exchange data between different systems and also to support different programming languages we picked up JSON format as our exchange format for data/objects. If needed, the server implementation can be eventually perfectioned, in a totally independent way, by specialized IT people. The second motivation is that if that we can benefit from the reuse of standardized API among different projects, in short, we don’t need to stick to a particular implementation. The main motivation is the widespread availability of free documentation and open software. Beside theoretical considerations, we evidentiate the greater comfort of using a standard architectural style versus a custom made solution. One possible architectural style for web services is the Representational State Transfer or in short form RESTful. At the end of the intro, you will be able to put at work your own simple web service. In particular, we are willing to share data with an Android device. Here we walk through a minimum working solution that can be used on DIY setups and was used in different Basic Air Data experimental projects. Now and then we are in need for a fast implementation of a CRUD web service, for example, to share data between heterogeneous digital systems. The proposed fast deployment solution was tested, in February 2017, on a Debian 7 Wheezy server with a dedicated IP and an Android Studio 2.2.3 generated Android client app.
0 kommentar(er)
