It sounds like you could easily do this with a publish-subscribe architecture?
Do you care if some messages are dropped?
--
Wolf
On Fri, Aug 31, 2012 at 12:37 AM, girish kumar girishbanga...@gmail.com wrote:
Hi All,
I really appreciate if any body solved these type of scenarios.
Thanks in
Hi,
Thanks for your response. So, in that case I can have multiple threads in
my NIO based server will become publishers(multiple) and another server
will become the subscriber.
I just curious to know, we can achieve better throughput only with
publish-subscribe messaging pattern.
Couple of
Hi All,
I really appreciate if any body solved these type of scenarios.
Thanks in advance.
On 29 August 2012 22:26, girish kumar girishbanga...@gmail.com wrote:
Hi All,
I am looking for a messaging pattern for the following scenario.
I have a Java NIO based server X, which has some
Hi All,
I am looking for a messaging pattern for the following scenario.
I have a Java NIO based server X, which has some threads processing client
requests. These threads receive events asynchronously. Now, I want to send
some of the events to another service(another server) Y in asynchronous
