Hands-On Software Engineering with Python

Requirements for a web-service-based daemon

If we were to pursue a web-service-based implementation for the Artisan Gateway instead, there are several common factors, and a few hurdles that would have to be overcome. Arguably the most significant hurdle would be in implementing the full set of HTTP methods – POST, GET, PUT, and DELETE – the official and standards-compliant methods that correspond to the Create, Read, Update, and Delete CRUD operations we're expecting to use.

If the medium that commands are transmitted in is to remain the serialized and signature-bearing message output of the DaemonMessage class, we'd need to be able to pass a complete, signed message in at least two different ways:

• In a query string format for the GET