[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [amqp-ms] List of non-normative references to amqp.org pages
|
Hi Ram, the purpose is to allow users, as well as developers of clients and brokers to register values which they wish to use for extensions so that a person using
a client from vendor X can use extensions which have been implemented by vendor Y in their broker. There is no requirement at all for implementers to have foresight as to what values may be defined in the future - if an implementation does not recognize a
capability then it will simply not offer it to the client. Mostly these fields are not on the AMQP Message but on the performatives for setting up entities such as connections, sessions, and links. The classic example that we often use is filter types. The specification defines where a filter (known in JMS as a selector) is passed from receiver to sender.
However the specification does not define any concrete syntaxes for filters at this time. We expect various different filter syntaxes to be proposed (e.g. SQL-style, XQuery, Regular Expressions, and so on). We may later define the implementation of some
of these filter types to be mandatory for some classes of AMQP implementation (e.g. the JMS Mapping will need to specify how implementations can provide JMS Selector style semantics). Other classes of JMS implementation (e.g. client applications) may not
need to have a native understanding of any of the filter types. -- Rob From: Ram Jeyaraman [mailto:Ram.Jeyaraman@microsoft.com]
If I understand this correctly, these URLs represent the “types” of the extended fields in a message. And we want to REQUIRE conformant implementations to use
these types (in their extended message fields) but the specification will NOT mandate what the values are that go inside those extended message fields. That is, a conformant implementation will understand and recognize these types but not necessarily the values.
Is that correct? Is that the intended semantics? Thanks. From: amqp-ms@lists.oasis-open.org [mailto:amqp-ms@lists.oasis-open.org]
On Behalf Of Angus Telfer Hi Rob, These aren't bad URL names ... why not use them directly or perhaps add "non-normative" somewhere if we want to make things absolutely clear (e.g. http://www.amqp.org/specification/non-normative/1.0/link-capabilities
)? cheers...angus On Nov-23-11, at 8:47 AM, Godfrey, Robert X wrote: All, as discussed at today’s Member Section Steering committee meeting, this is the current list of URLs to location within amqp.org holding
repositories of properties/capabilities: http://www.amqp.org/specification/1.0/connection-capabilities Cheers, Rob This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal
privilege, and legal entity disclaimers, available athttp://www.jpmorgan.com/pages/disclosures/email. This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]