| Hi guys,
It's fantastic news that we have people that care about this. I would like to suggest that someone take the lead (like Laurie has in the MS Goal group and Ram in the Transfer group) and put out an email say that we're going to put together a small group to discuss this issue and resolve it. Anyone interested can then email that person and (voila) we have a group of interested parties that can get the job done quickly.
What say? Who's willing to play the lead role (doesn't have to be the most technical person ... often a good idea if it isn't)?
cheers...angus
On Feb-14-12, at 9:42 AM, Raphael Cohn wrote: (a) I believe Rob and I forwarded you on an old proposal of a filter language. This would need some reworking to take advantage of the late improvements to the codec, but would provide an effective way to do extremely powerful filtering.
(b) So yes, there's some content
(c) Yes, I think a group's an excellent idea. I'd be happy to contribute what we have for others to play with.
Right now, though, we're keen to put all our efforts into getting the CSD and final AMQP 1-0 spec out the door.
Raph Raphael Cohn Chief Architect, StormMQ Secretary, OASIS AMQP Standard
raphael.cohn@StormMQ.comStormMQ 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.comOn 14 February 2012 17:22, Andreas Mueller <am@iit.de> wrote:
Filters are not part of the spec; they are maintained in a registry (non-normative refs) on the AMQP/OASIS web site.
What I want to know is
a) what ideas have been discussed already?
b) is there already content, e.g. filters, capabilities?
c) is it necessary to create a sub-group or can we just maintain it in a nonformal way?
Important for me as a JMS provider is to get 2 AMQP-registered filters, NoLocal and JMS Selector, which can be shared among JMS providers.
Currently I'm using these 2 filters but with IANA numbers for IIT. So these filters work fine with SwiftMQ but no other JMS provider will recognize the descriptor code as a NoLocal or JMS Selector filter.
Am 14.02.2012 um 17:13 schrieb Gordon Sim:
> I think we want a simple way for implementers and communities to experiment with particular extensions prior to any standardisation effort by OASIS. Filtering is an obvious area for this sort of thing and there are others.
>
> That's not to say a formal standard is not a good thing. It is simply that we want to allow emergence of 'grass-roots' interoperable extensions before getting a full standard out.
>
> My suggestion would be to use symbolic descriptors either in a domain assigned to experimental work or conforming to a particular pattern (e.g. prefixed by 'x-').
>
> These would not be official OASIS standards at this point but would allow collaborative efforts externally to be useful to users and to prove out different approaches which would be valuable feedback into any standardisation effort.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: amqp-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: amqp-help@lists.oasis-open.org
>
|