ASYNC / Concurreny Web Protocols Web Servers and MicroFWs (Flask/Tornado/Nginx/...)
See in scheduleIn this talk I'm going to live code a web application that is built exclusively on top of WebSocket, without using HTTP at all!
What's the benefit of using WebSocket over HTTP, you may ask? With WebSocket each client establishes a permanent connection to the server, so there is no request/response cycle and no need for the client to poll the server for data. Each side can freely send data to the other side at any time, so this is an ideal stack for building highly dynamic, event-driven applications.
For this live coding exercise I'm going to use the Socket.IO server for Python, and the Socket.IO client for JavaScript. No Flask, no Django, no HTTP!
Type: Talk (60 mins); Python level: Intermediate; Domain level: Intermediate
Miguel Grinberg wrote his first line of code in 1983 and hasn't stopped coding since. He blogs at https://blog.miguelgrinberg.com about a variety of topics including web development, Python, robotics, photography and the occasional movie review. Miguel is the author of the Flask Mega-Tutorial and the O'Reilly book "Flask Web Development". He calls Portland, Oregon home, but is currently on a "working vacation" in Ireland.
