On 09/27/2013 01:09 AM, Mitsuru Oka wrote:
2013/9/25 Ted Ross :
Load-balanced fan-out is not currently implemented but is something that I
consider a key feature. I'd be interested to hear if you have specific
requirements for how it works.
One interesting request I've heard is to be able to
2013/9/25 Ted Ross :
> Load-balanced fan-out is not currently implemented but is something that I
> consider a key feature. I'd be interested to hear if you have specific
> requirements for how it works.
>
> One interesting request I've heard is to be able to establish groups of
> consumers for a
On 09/26/2013 03:28 PM, Ted Ross wrote:
On 09/26/2013 08:23 AM, Gordon Sim wrote:
On 09/26/2013 01:14 PM, Ted Ross wrote:
I'm putting a feature into Dispatch that allows a client to dynamically
obtain a routable reply-to address. This will involve changes in
Messenger as well.
I'd be intere
On 09/26/2013 03:28 PM, Ted Ross wrote:
On 09/26/2013 08:23 AM, Gordon Sim wrote:
On 09/26/2013 01:14 PM, Ted Ross wrote:
I'm putting a feature into Dispatch that allows a client to dynamically
obtain a routable reply-to address. This will involve changes in
Messenger as well.
I'd be intere
On 09/26/2013 08:23 AM, Gordon Sim wrote:
On 09/26/2013 01:14 PM, Ted Ross wrote:
I'm putting a feature into Dispatch that allows a client to dynamically
obtain a routable reply-to address. This will involve changes in
Messenger as well.
I'd be interested in hearing a bit more about that, wi
2013/9/26 Ted Ross :
> First, modify your client line to include a reply-to address.
>
>
> $ dispatch-router -c qpid-dispatch.conf
> $ ./server.py amqp://0.0.0.0/topic
> $ ./client.py -r amqp://0.0.0.0/reply amqp://0.0.0.0/topic subject
>
>
> You will also need to apply the following pa
On 09/26/2013 01:14 PM, Ted Ross wrote:
I'm putting a feature into Dispatch that allows a client to dynamically
obtain a routable reply-to address. This will involve changes in
Messenger as well.
I'd be interested in hearing a bit more about that, with a view to
making any necessary changes t
On 09/26/2013 12:03 AM, Mitsuru Oka wrote:
Another question on Dispatch router is there.
Could you show me an example of request-reply/response pattern via
Dispatch router using proton messenger based sender and receiver? I
tried proton client/server python example, but the client couldn't
recei
On 09/26/2013 05:03 AM, Mitsuru Oka wrote:
Another question on Dispatch router is there.
Could you show me an example of request-reply/response pattern via
Dispatch router using proton messenger based sender and receiver? I
tried proton client/server python example, but the client couldn't
recei
Another question on Dispatch router is there.
Could you show me an example of request-reply/response pattern via
Dispatch router using proton messenger based sender and receiver? I
tried proton client/server python example, but the client couldn't
receive reply message from server.
$ dispatch-rou
On 09/25/2013 07:49 AM, Gordon Sim wrote:
On 09/16/2013 09:57 PM, Ted Ross wrote:
The following is a brief example of the router's use to illustrate how
it works:
[Refer to the README file for building instructions]
[The router executable and Proton Messenger examples are assumed to be
in the
This sounds like a good use case for Dispatch Router. Please let me
know if there is any way I can be of help to you.
-Ted
On 09/25/2013 10:18 AM, Mitsuru Oka wrote:
I am considering use of Dispatch Router for asynchronous task queue like
Celery framework. But Celery is based on a broker such
I am considering use of Dispatch Router for asynchronous task queue like
Celery framework. But Celery is based on a broker such as RabbitMQ. I just
dont want to use such the heavy broker, because the task is no need to be
durable. So, the Dispatch Router is relative good choice for me.
If two or
On 09/25/2013 09:20 AM, Gordon Sim wrote:
On 09/25/2013 02:14 PM, Ted Ross wrote:
Load-balanced fan-out is not currently implemented but is something that
I consider a key feature. I'd be interested to hear if you have
specific requirements for how it works.
What about selective subscription
On 09/25/2013 02:14 PM, Ted Ross wrote:
Load-balanced fan-out is not currently implemented but is something that
I consider a key feature. I'd be interested to hear if you have
specific requirements for how it works.
What about selective subscriptions e.g. sub-topic matching or wildcard
match
Load-balanced fan-out is not currently implemented but is something that
I consider a key feature. I'd be interested to hear if you have
specific requirements for how it works.
One interesting request I've heard is to be able to establish groups of
consumers for a "topic". A message will be
On 09/16/2013 09:57 PM, Ted Ross wrote:
The following is a brief example of the router's use to illustrate how
it works:
[Refer to the README file for building instructions]
[The router executable and Proton Messenger examples are assumed to be
in the execution path]
Run the following in separa
Hello, I'm new to Proton and Dispatch router.
I'd like to know if the Dispatch Router support more complex patterns
such as pub-sub. Especially, whether load balanced routing to
subscribe node is implemented or not is my interesting point.
Thanks,
Mitsuru Oka
2013/9/17 Ted Ross :
> I've been wo
patch/src/server.c: In function ‘thread_process_listeners’:
>>>>>> dispatch/src/server.c:103: error: implicit declaration of function
>>>>>> ‘pn_connector_name’
>>>>>> make[2]: *** [CMakeFiles/qpid-dispatch.dir/src/server.c.o] Error 1
>>>>&g
lp@.apache
-
To unsubscribe, e-mail:
users-unsubscribe@.apache
For additional commands, e-mail:
users-help@.apache
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Introducing-Qpid-Dispatch-Router-tp7598222p7598248.html
2
>>>> make: *** [all] Error 2
>>> Do you have the latest proton libraries (0.5) and is the cmake build
>>> configured to point at them?
>>>
>>>
>>> -
nt at them?
-
To unsubscribe, e-mail:
users-unsubscribe@.apache
For additional commands, e-mail:
users-help@.apache
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Introducing-Qpid-Dispatch-Router-tp7598222p7598230.html
Sent from the Apache Qpid users ma
users-unsubscribe@.apache
> For additional commands, e-mail:
> users-help@.apache
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Introducing-Qpid-Dispatch-Router-tp7598222p7598230.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
On 09/17/2013 07:59 AM, NimbusParc wrote:
Error while doing make ..
dispatch/src/server.c: In function ‘thread_process_listeners’:
dispatch/src/server.c:103: error: implicit declaration of function
‘pn_connector_name’
make[2]: *** [CMakeFiles/qpid-dispatch.dir/src/server.c.o] Error 1
make[1]: **
essages to their respective addresses.
>
> If everything works, the first sent message will be received by the
> first two receivers and the second sent message will be received only by
> the third receiver.
>
> Regards,
>
> -Ted
--
View this message in context:
http://
I've been working on a sub-project within Apache Qpid called Qpid
Dispatch Router. I'd like to invite use, participation, feedback,
criticism, etc.
There are a couple of basic introductory points to be made:
* Dispatch Router is built on top of the Qpid Proton engine and driver
APIs (The
26 matches
Mail list logo
