Using an MQeQueue as the local registry for a pervasive client
Original Publication Date: 2001-Sep-16
Included in the Prior Art Database: 2003-Jun-20
Disclosed is an example of use of a messaging product such as IBM's MQSeries* Everyplace* product. Currently clients running a messaging product such as the MQSeries Everyplace product have a local registry that contains the configuration and running information for that client. This requires separate forms of security, authorisation and update. By creating a simple descendent of the normal MQeQueue class you can create a class that will function as a repository for registry information. This would automatically give all the security controls associated with a Queue to the local registry. I.e. only the authorised people would be able to access or update the Queue).