Book Image

Building SPAs with Django and HTML Over the Wire

By : Andros Fenollosa
5 (1)
Book Image

Building SPAs with Django and HTML Over the Wire

5 (1)
By: Andros Fenollosa

Overview of this book

The HTML over WebSockets approach simplifies single-page application (SPA) development and lets you bypass learning a JavaScript rendering framework such as React, Vue, or Angular, moving the logic to Python. This web application development book provides you with all the Django tools you need to simplify your developments with real-time results. You’ll learn state-of-the-art WebSocket techniques to realize real-time applications with minimal reliance on JavaScript. This book will also show you how to create a project with Docker from the ground up, test it, and deploy it on a server. You’ll learn how to create a project, add Docker, and discover development libraries, Django channels, and bidirectional communication, and from then, on you’ll create real projects of all kinds using HTML over WebSockets as a chat app or a blog with real-time comments. In addition, you’ll modernize your development techniques by moving from using an SSR model to creating web pages using WebSockets over HTML. With Django, you’ll be able to create SPAs with professional real-time projects where the logic is in Python. By the end of this Django book, you’ll be able to build real-time applications, as well as gaining a solid understanding of WebSockets with Django.
Table of Contents (14 chapters)
Part 1: Getting Started with Python
Part 2: WebSockets in Django
Part 3: HTML over WebSockets
Part 4: Simplifying the frontend with Stimulus


We have been able to connect a consumer to a database to manage its information and reply with new rendered HTML structures that we have injected. Gradually, a very basic real-time social network has been built to insert messages, list them, filter them, update them, and delete them. The frontend has a simple role – handling events, sending data, and receiving HTML via WebSockets.

Currently, there are several limitations related to group discrimination. When an action is performed, it is propagated to all users, meaning all actions have an impact on all visitors at the same time. Basically, that’s a good thing that we want it to happen, but not in all flows. Do I want everyone to update their message listings when a new message is inserted? Yes, of course – and when editing or deleting. Although it should be avoided for certain actions that should be private. At the moment, if one user changes page, everyone changes page. That’s why we are going...