On Thu, Mar 28, 2013 at 03:11:51PM -0400, Alan Conway wrote:
> I am starting to think we need a proton routing plug-in API so that
> different choices of routing rules, pattern matching, configuration
> files etc. can be implemented without baking one set of choices into
> messenger. Such a plugin
without baking one set of choices into messenger. Such a plugin API
could be fairly simple and would allow choice and composition of functionality
from different plug-ins.
- Original Message -
From: "Rafael Schloming"
To: proton@qpid.apache.org
Sent: Saturday, March 23, 2013 12
On Thu, Mar 28, 2013 at 8:59 AM, Ken Giusti wrote:
> Not to hijack this thread, but...
>
> Yes, absolutely - this is a Must Have as far as I'm concerned.
> Specifically:
>
> 1) The application should control whether Reply-to is set or not
> (currently always set by messenger)
> 2) The application
outes precedence based on their restrictiveness - matching more
restrictive first?
-K
- Original Message -
> From: "Rafael Schloming"
> To: proton@qpid.apache.org
> Sent: Saturday, March 23, 2013 12:43:07 PM
> Subject: RFC: new routing functionality for messenger
>
Not to hijack this thread, but...
- Original Message -
> From: "Rafael Schloming"
> To: proton@qpid.apache.org
> Sent: Tuesday, March 26, 2013 10:00:23 AM
> Subject: Re: RFC: new routing functionality for messenger
>
> On Tue, Mar 26, 2013 at 7:19 AM, Bozo Dr
On Wed, Mar 27, 2013 at 8:55 AM, Ted Ross wrote:
>
> On 03/25/2013 09:30 AM, Rafael Schloming wrote:
>
>> On Mon, Mar 25, 2013 at 8:36 AM, Ted Ross wrote:
>>
>> I question the value of having this as part of the API. It seems to me
>>> that the Messenger routing table should be part of the con
On 03/25/2013 09:30 AM, Rafael Schloming wrote:
On Mon, Mar 25, 2013 at 8:36 AM, Ted Ross wrote:
I question the value of having this as part of the API. It seems to me
that the Messenger routing table should be part of the configuration of a
system (i.e. in a place like /etc/qpid/messenger/,
On Tue, Mar 26, 2013 at 2:13 PM, Alan Conway wrote:
> On 03/25/2013 09:30 AM, Rafael Schloming wrote:
>
>> On Mon, Mar 25, 2013 at 8:36 AM, Ted Ross wrote:
>>
>> I generally like this translation facility, though I'll need to think
>>> through some use cases to make sure there's sufficient capa
On 03/25/2013 09:30 AM, Rafael Schloming wrote:
On Mon, Mar 25, 2013 at 8:36 AM, Ted Ross wrote:
I generally like this translation facility, though I'll need to think
through some use cases to make sure there's sufficient capability in the
matching and substitution.
I would definitely appre
On Tue, Mar 26, 2013 at 7:19 AM, Bozo Dragojevic wrote:
> On 3/23/13 5:43 PM, Rafael Schloming wrote:
>
>> Hi,
>>
>> I've added a new API to messenger that gives the user some control over
>> the
>> internal routing behaviour of a messenger. Please check it out and
>> comment.
>> I've pasted the
On 3/23/13 5:43 PM, Rafael Schloming wrote:
Hi,
I've added a new API to messenger that gives the user some control over the
internal routing behaviour of a messenger. Please check it out and comment.
I've pasted the C API/doxygen below. This is currently only exposed through
the python binding v
On 3/25/13 8:26 PM, Rafael Schloming wrote:
On Mon, Mar 25, 2013 at 3:06 PM, Bozo Dragojevic wrote:
Rafael,
did you consider a variant where a user can supply a rewrite object?
pn_messenger_set_router(pn_**messenger_t *msgr, pn_router_t *router)
Proton library can then easily supply a one o
On Mon, Mar 25, 2013 at 3:06 PM, Bozo Dragojevic wrote:
> Rafael,
>
> did you consider a variant where a user can supply a rewrite object?
>
> pn_messenger_set_router(pn_**messenger_t *msgr, pn_router_t *router)
>
> Proton library can then easily supply a one or more ready-made
> implementations.
Rafael,
did you consider a variant where a user can supply a rewrite object?
pn_messenger_set_router(pn_messenger_t *msgr, pn_router_t *router)
Proton library can then easily supply a one or more ready-made
implementations.
Bozzo
On 3/23/13 5:43 PM, Rafael Schloming wrote:
Hi,
I've added
On Mon, Mar 25, 2013 at 11:42 AM, Rafael Schloming wrote:
> On Mon, Mar 25, 2013 at 10:34 AM, Rajith Attapattu wrote:
>
>> For starters I would copy this email to the user list.
>> (In the future we should post things like this to a more wider
>> audience, especially if we are looking for feedback
On Mon, Mar 25, 2013 at 10:34 AM, Rajith Attapattu wrote:
> For starters I would copy this email to the user list.
> (In the future we should post things like this to a more wider
> audience, especially if we are looking for feedback based on real
> world use cases.)
>
I posted it where I intende
For starters I would copy this email to the user list.
(In the future we should post things like this to a more wider
audience, especially if we are looking for feedback based on real
world use cases.)
I actually like the minimalistic approach you've taken here. It works
well in an embedded contex
On Mon, Mar 25, 2013 at 8:36 AM, Ted Ross wrote:
> I generally like this translation facility, though I'll need to think
> through some use cases to make sure there's sufficient capability in the
> matching and substitution.
>
I would definitely appreciate some more feedback on this area. I thin
I generally like this translation facility, though I'll need to think
through some use cases to make sure there's sufficient capability in the
matching and substitution.
I question the value of having this as part of the API. It seems to me
that the Messenger routing table should be part of t
Hi,
I've added a new API to messenger that gives the user some control over the
internal routing behaviour of a messenger. Please check it out and comment.
I've pasted the C API/doxygen below. This is currently only exposed through
the python binding via the route method on the Messenger class.
-
20 matches
Mail list logo
