Book Image

Python Web Development with Sanic

By : Adam Hopkins
Book Image

Python Web Development with Sanic

By: Adam Hopkins

Overview of this book

Today’s developers need something more powerful and customizable when it comes to web app development. They require effective tools to build something unique to meet their specific needs, and not simply glue a bunch of things together built by others. This is where Sanic comes into the picture. Built to be unopinionated and scalable, Sanic is a next-generation Python framework and server tuned for high performance. This Sanic guide starts by helping you understand Sanic’s purpose, significance, and use cases. You’ll learn how to spot different issues when building web applications, and how to choose, create, and adapt the right solution to meet your requirements. As you progress, you’ll understand how to use listeners, middleware, and background tasks to customize your application. The book will also take you through real-world examples, so you will walk away with practical knowledge and not just code snippets. By the end of this web development book, you’ll have gained the knowledge you need to design, build, and deploy high-performance, scalable, and maintainable web applications with the Sanic framework.
Table of Contents (16 chapters)
Part 1:Getting Started with Sanic
Part 2:Hands-On Sanic
Part 3:Putting It All together

Chapter 4: Ingesting HTTP Data

The next building block in application development involves data. Without data, the web has little utility. I do not mean to get too philosophical here, but it is axiomatic that the purpose of the internet is the facilitation of the transfer of data and knowledge from one location to another. Therefore, it is critical to our development as web professionals to learn how data can be transferred not just from our applications (which we deal with in Chapter 5, Building Response Handlers), but also to our applications (which is the purpose of this chapter). The simplest applications we can build simply provide data. However, to become interactive web applications participating in the global exchange of knowledge, even simple applications must be capable of extracting data from web requests.

A web application that receives no data is like a screencast. Viewers can come to watch the presentation, but the presenter has no personal connection to the people...