When you have out-of-band processing in a web app, how do you let users know
that the status of a task has changed? Depending on your front-end client,
there are a few different approaches you might take.
Transmitting objects between web processes and worker processes is a
requirement of many modern web apps. Given that the safest way to do so is to
use a serialization format that only includes primitive data types, how can
we send custom objects around?
We want the convenience of a client-side single-page application using our
MV* frameworkof choice, but don’t want to sacrifice the SEO and UX
benefits of rendering the initial markup on the server. And while we’re not
tech stack. Here’s our attempt to have the best of both worlds, all the while
keeping duplication of logic or code between the front-end and back-end
worlds to a minimum.
SQLAlchemy defaults to implicitly opening a new transaction on your first
database query. If you prefer to start your transactions explicitly instead,
I’ve documented here my explorations in getting that to work.