A bit of reorganization
Before digging into the details of the individual transactions, some minor reorganization of recent code seems in order. The RabbitMQSender and DaemonMessage classes were originally written in the hms_core.daemons module, because that seemed a logical place to keep them—they are still relevant to the daemon, but also have relevance to parts of the Artisan Application (and perhaps the Central Office application) that don't have any ties to the various daemon classes themselves. Since we've also uncovered a need for various objects to be able to generate message data structures, and that feels like it should be handled by a different abstraction, it feels logical to move those two classes into a new hms_core module ( ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access