QMFv2 Project Page

Introduction

This developer page shall be used to collect architecture, design, and project information for the development of the Qpid Management Framework. It will become the basis for a distilled, user-oriented set of documentation.

• Architecture
• Protocol
• Design
• APIs

Changes from Version 1

• Broker participation in QMF is no longer mandatory. In QMFv1, the broker provides two essential services for QMF: Agent registration and Schema caching. In QMFv2, the need for agent registration has been removed. Schema caching remains a valuable optimization but is not required in QMFv2.

...

• Agents no longer publish data globally. Global publishing of data by agents causes security and scaling issues. In QMFv2, the global publish is replaced by subscription queries where a console establishes a subscription and receives periodic updates about changes to data in its field of interest. The benefits are that the query can be authorized based on an authenticated user-id and that data is not generated if there are not consoles interested in receiving that data.

Backward/Forward Compatibility with QMFv1

The following compatibility matrix shows all combinations of V1 and V2 components (console, agent, and broker). Those intersections marked "OK" are supported without the need for compatibility-oriented development.

...

• The features in notes 1 and 2 must be implemented. It is important that users not be required to upgrade all components of their deployments at the same time.
• The feature in note 3 may be implemented. This is considered lower priority.
• The feature in note 4 shall not be implemented. Because QMF V2 is intended to scale to larger networks than are currently possible with V1, and this feature would limit the scalability of QMF V2, this is considered non-desirable.

Development Roadmap