Thanks Patrik,
The pub/sub code works. It was really simple to work with.
On Tuesday, 6 May 2014 16:40:01 UTC+1, Patrik Nordwall wrote:
That is how topics are implemented (but not with the eventbus). A message
published to a topic is only transferred over the wire once to each node
that
On Wed, May 7, 2014 at 10:01 AM, Jabbar Azam aja...@gmail.com wrote:
Thanks Patrik,
The pub/sub code works. It was really simple to work with.
You're welcome. Glad to hear that.
/Patrik
On Tuesday, 6 May 2014 16:40:01 UTC+1, Patrik Nordwall wrote:
That is how topics are implemented
Hello Endre,
What about one actor from each node joining the DistributedPubSubMediator
and this actor could register with a node local Akka eventbus? The sharded
actors could register with the local Akka event bus for messages.
So a message published to a topic, on the
Hi Jabbar,
We were thinking of that same design. If you implement before we do, please
share your experiences with that design and we will do the same.
Chanan
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Hello Chanan,
This is an evening project for me so you might get it done before me.
Although I got the cluster sharding, with cassandra, working last night.
On Tuesday, 6 May 2014 14:14:19 UTC+1, Chanan Braunstein wrote:
Hi Jabbar,
We were thinking of that same design. If you implement
Hi Jabbar,
No, you are not missing anything, PubSub is designed for such cases. Just
be careful not to broadcast too much data since it does not scale linearily.
-Endre
On Sat, May 3, 2014 at 1:06 AM, Jabbar Azam aja...@gmail.com wrote:
I've just looked at the documentation. I can use the
I've just looked at the documentation. I can use the
DistributedPubSubMediator and get all the sharded actors listening to a
topic. So when I need the contents from a particular sharded actor I can
send a message to a topic which will be received by all the sharded actors
and the one
