Re: [akka-user] Connection state in Artery

I will, thanks for your feedback, much appreciated! :) Op maandag 13 november 2017 17:10:28 UTC+1 schreef Patrik Nordwall: > > > > On Mon, Nov 13, 2017 at 4:43 PM, Merlijn Boogerd > wrote: > >> Hi Patrik, >> >> Thanks for your fast response! >> >> > In general we

Re: [akka-user] Connection state in Artery

On Mon, Nov 13, 2017 at 4:43 PM, Merlijn Boogerd < merlijn.boog...@trivento.nl> wrote: > Hi Patrik, > > Thanks for your fast response! > > > In general we recommend against using Akka Remoting without Akka > Cluster, but you might have good reasons for not using Akka Cluster? > > My reason to not

Re: [akka-user] Connection state in Artery

Hi Patrik, Thanks for your fast response! > In general we recommend against using Akka Remoting without Akka Cluster, but you might have good reasons for not using Akka Cluster? My reason to not use Cluster is because its complete view of the cluster members poses a scalability issue beyond

Re: [akka-user] Connection state in Artery

Hi Merlijn, On Sun, Nov 12, 2017 at 5:02 PM, Merlijn Boogerd < merlijn.boog...@trivento.nl> wrote: > Hi fellow hakkers, > > I have two questions regarding the Artery module (I am not considering the > previous remoting as it will eventually get deprecated). I implemented a > peer sampling

[akka-user] Connection state in Artery

Hi fellow hakkers, I have two questions regarding the Artery module (I am not considering the previous remoting as it will eventually get deprecated). I implemented a peer sampling service (HyParView) and am in the process of implementing a clustering service (Vicinity), both directly on top