Get money for playing games for free

Swagger and Flask Tutorial

Introduction

• API documentation is important.
• Coding to Interfaces and Separation of Concerns remain fundamental design patterns
• Any project involving a great deal of source code and multiple developers will likely fail without proper attention to this design
• Exposing Functionality is important
• This conveys and demonstrates progress 
• In a proper SOA design, functionality is exposed as a series of internal business processes
• Business Processes are APIs
• By using Swagger to document the APIs we get an auto-generated user interface that both documents and helps a (somewhat technical) user explore the dialog functionality
• Any Tester or Business Analyst role should have the skill to navigate a Swagger-generated API, view the documentation, and explore a variety of I/O possibilities

API Documentation in Swagger

Generate a Python Flask app from the YAML markup

Fixing the Generated Code

1. Each method was generated into a separate python file (<name>_controller.py).  There was a casing issue that I had to correct. 
   
   The swagger.yaml file had this
   operationId: "controllers.Occurences_controller.ups_global_get"
   
   and I had to change that to this:
   operationId: "controllers.occurences_controller.ups_global_get"
   
   in order to correspond to the actual casing of the python file.
2. Likewise, the generated code was initially configured to run the swagger UI on port 80 and the operations on port 8080. 
   
   This caused some trouble, as the endpoint operation couldnt figure out which port to use when.
   
   It became a lot easier when I changed this line from
   host: "localhost"
   to
   host: "localhost:5000"
   and alter app.py to run on 5000 as well:
   

   app.run(port=5000)

3. The generated code needs some changing:

Running the App

References

1. Swagger Tutorial
2. Online Swagger Editor

download file now

Summary of “A Tutorial Survey on Vehicular Ad Hoc Networks”

1. Adaptation and decreasing cost of IEEE 802.11 technologies
2. The embrace of vehicle manufactures of information technology to provide safety and comfort
3. The commitment of large government to allocate wireless spectrum for VANET communication

1. Road safety
2. Transportation efficiency
3. Reduce the impact of transportation on the environment

1. Event-driven (DEN)

2. Periodic (CAM)

1. The main challenges of VANET is as follow:
2. No central communication coordinator or handshaking protocol
3. The necessity of on shared control channel to broadcast each cars knowledge to the surroundings
4. Dynamic network topology
5. Diversity of network traffic density

download file now