In order to actually do something with the data of a message, we'll need to define what a well-formed command message actually looks like, implement methods to execute the commands that are allowed, and implement functionality that knows how to call those methods, given a well-formed and verified message to do so. The first item from that list is quite simple, but could have a lot of different valid implementation patterns. Consider that, at this point, we're allowed to transmit four different operation actions by DaemonMessage: 'create', 'update', 'delete', and 'response'. These operation actions correspond directly to standard CRUD operations, except for the 'response' value, though even that is, perhaps, roughly equivalent ...
Handling messages
Get Hands-On Software Engineering with Python now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.