Re: [amqp] Non-normative Refs: Filters

[Andreas Mueller <am@iit.de>]

I would prefer to have exactly such a provider-dependend opaque filter that could be a JMS selector, regex whatever. AMQP does not need to define the syntax/semantics of the filter. It just needs to provide a way to pass a filter to the broker.

-- 
Andreas Mueller
IIT Software GmbH, Bremen/Germany
http://www.swiftmq.com

Am 14.02.2012 um 13:02 schrieb Raphael Cohn:

> Yes, but we need to make sure that a decision in haste now doesn't cripple a good standard. And I'd actually argue it'd be far more preferable to have a filtering mechanism that is a superset of the world capable of representing such needs, rather than opaque text strings. A rhetorical questions that springs to mind - are you planning to put in JMS versioning in those filters? There's a lot here.
> 
> It's an open conversation that's only just started, and can have many conclusions. I'd like to rope in Dave, Rob, and Rafi, too, when we're finished on the CSD, because they've all expressed interesting views here.
> 
> Raph
> 
> Raphael Cohn
> Chief Architect, StormMQ
> Secretary, OASIS AMQP Standard
> raphael.cohn@StormMQ.com
> StormMQ Limited
> 
> UK Office: 
> Gateshead int'l Business Centre, Mulgrave Terrace, Gateshead, NE8 1AN, United Kingdom
> Telephone: +44 845 3712 567
> 
> Registered office:
> 16 Anchor Street, Chelmsford, Essex, CM2 0JY, United Kingdom
> StormMQ Limited is Registered in England and Wales under Company Number 07175657
> StormMQ.com
> 
> 
> 
> On 14 February 2012 12:01, Andreas Mueller <am@iit.de> wrote:
> I doubt that we need filters that can interoperate with everything. I just need a JMS filter that can is understood by JMS providers. OpenMAMA doesn't need to understand that filter and I don't need to understand a SMTP filter.
> 
> --
> Andreas Mueller
> IIT Software GmbH, Bremen/Germany
> http://www.swiftmq.com
> 
> Am 14.02.2012 um 12:44 schrieb Raphael Cohn:
> 
> > I think we need to start a sub-group, and define a process for filter extensions. Filters are a complex subject, and JMS isn't the only use case they need to support. Even then, a JMS selector needs to have a defined mapping to AMQP concepts.
> >
> > In particular, there's a need for more than one 'dialect', particularly so we can interoperate with OpenMAMA, MQTT, SMTP and, preferably, a native AMQP encoding which allows to access the full fidelity of information present in AMQP structured messages.
> >
> > Raph
> >
> > Raphael Cohn
> > Chief Architect, StormMQ
> > Secretary, OASIS AMQP Standard
> > raphael.cohn@StormMQ.com
> > StormMQ Limited
> >
> > UK Office:
> > Gateshead int'l Business Centre, Mulgrave Terrace, Gateshead, NE8 1AN, United Kingdom
> > Telephone: +44 845 3712 567
> >
> > Registered office:
> > 16 Anchor Street, Chelmsford, Essex, CM2 0JY, United Kingdom
> > StormMQ Limited is Registered in England and Wales under Company Number 07175657
> > StormMQ.com
> >
> >
> >
> > On 14 February 2012 11:04, Andreas Mueller <am@iit.de> wrote:
> >
> > Am 07.02.2012 um 10:32 schrieb Andreas Mueller:
> >
> >> Currently I'm using these filter declarations:
> >>
> >> <section name="filter-types">
> >>      <type class="composite" name="no-local-filter" source="list" provides="filter">
> >>              <descriptor name="amqp:no-local-filter:list" code="0x0000412B:0x00000000"/>
> >>      </type>
> >>      <type class="restricted" name="jms-selector-filter" provides="filter" source="string">
> >>              <descriptor name="amqp:jms-selector-filter:string" code="0x0000412B:0x00000001"/>
> >>      </type>
> >> </section>
> >
> > Well, I can't continue here until I know from which range I can use to generate descriptor code for the above filters. The current code 0x0000412B is the IANA code for IIT. But it's important that we have a code assigned from AMQP to ensure that all brokers capable of using NoLocal and JMS filters understand the very same filters.
> >
> > I suggest we use a range from 200 to 255 for filters so the above no-local-filter would have code 0x00000000:0x000000C8 and the jms-selector-filter code  0x00000000:0x000000C9.
> >
> > What do I need to do to get this done?
> >
> > --
> > Andreas Mueller
> > IIT Software GmbH, Bremen/Germany
> > http://www.swiftmq.com
> >
> >
> >
> >
> >
> > IIT Software GmbH
> > Fahrenheitstr. 1, D28359 Bremen, Germany
> > Tel: +49 421 2208-166, Fax: +49 421 2208-167
> > Amtsgericht Bremen, HRB 18624, Geschaeftsfuehrer: Andreas Mueller
> > Steuernummer: 71/572/04100, VAT: DE199945912
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: amqp-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: amqp-help@lists.oasis-open.org
> >
> >
> 
> 
> 
> 
> 
> IIT Software GmbH
> Fahrenheitstr. 1, D28359 Bremen, Germany
> Tel: +49 421 2208-166, Fax: +49 421 2208-167
> Amtsgericht Bremen, HRB 18624, Geschaeftsfuehrer: Andreas Mueller
> Steuernummer: 71/572/04100, VAT: DE199945912
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: amqp-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: amqp-help@lists.oasis-open.org
> 
> 






IIT Software GmbH
Fahrenheitstr. 1, D28359 Bremen, Germany
Tel: +49 421 2208-166, Fax: +49 421 2208-167
Amtsgericht Bremen, HRB 18624, Geschaeftsfuehrer: Andreas Mueller
Steuernummer: 71/572/04100, VAT: DE199945912