Here’s a snapshot of the state of the Management document overhaul:
https://1drv.ms/w/s!AgcBsXoqzTwSreVu-UCw8nbAP2X9CA
I believe the reality of the wire is still largely intact for the core CRUD functions, but I’ve been doing quite a bit of detail clarification work that reinterprets some of the relationships. As I keep going, there will
be some wire impact for the discovery and metadata functions.
Von: Clemens Vasters
Gesendet: Mittwoch, 12. September 2018 18:51
An: Ted Ross <tross@redhat.com>; amqp@lists.oasis-open.org
Betreff: AMQP management
Hi Ted,
I just started giving AMQP Management the required makeover and I’d like to simplify a few aspects. Rob said that you’ll be most interested in any changes I might have in mind.
First, I’d like to reduce the conceptual framework {entity type, type, type annotation} down to the simple notion that entity metadata set/updated via management is just a map of attributes
with a handful of mandatory common attributes (identity and type) that must exists for any entity. Except for annotations, whose practical purposes don’t reveal themselves to me in the spec, the wire impact of simplifying that should be minimal.
Second, I’m planning to change all operations to use request/response over link pairing as a preference. Correlated request/response should still work, nevertheless.
Regarding operations, I’m interested in which operations are currently in active use in the RH/Apache projects.
Thank you
Clemens
|
|
Clemens Vasters Messaging Platform Architect Microsoft Azure È+49 151 44063557 *
clemensv@microsoft.com
|
