Since Artisans will communicate with the Gateway over specific queues, and those queues have to be identified and consistently associated with their respective Artisans, we'll need to have mechanisms in the various code bases to store queue identifiers, and to associate them with their Artisan owners.
The queue specifications themselves can be implemented simply by adding a property (queue_id) to the Artisan objects' classes. Since the Artisan objects at both the Gateway service and Artisan application will make use of queue_id, it makes sense to implement that in the hms_core.business_objects.BaseArtisan class, where it will be inherited everywhere it's needed. The property getter and deleter methods ...
