search

He-Pin / akka-remote-transport-netty4

akka remote transport implemented by netty4
Apache License 2.0
7 stars 1 forks source link

Conflicting config in reference.conf #2

Open patriknw opened 9 years ago

patriknw commented 9 years ago

Defining settings in the reference.conf that are already defined in akka-remote reference.conf is not going to work in a deterministic way. Which value that gets used is undefined (depending on classpath order?).

You should probably document those instead and let user define them in their application.conf

The properties in question:

enabled-transports = ["akka.remote.netty4.tcp"]
use-dispatcher = "akka.remote.default-remote-dispatcher"
default-remote-dispatcher {
  type = Dispatcher
  executor = "fork-join-executor"
  fork-join-executor {
    # Min number of threads to cap factor-based parallelism number to
    parallelism-min = 8
    parallelism-factor = 2.0
    parallelism-max = 32
  }
}
He-Pin commented 9 years ago

sorry for that.This is under developing ,and I will update the document about something I think in the README.

currently we are using it for our game server,so I just copy and paste. I will going to add ssl , udp and docker support . I will do that.thanks you .and maybe add crossCompile.

the only different in this project are this. 1,no channel local,binding via trigger event 2,may using native epoll transport in netty4 3,could merge write via flush tick 4,via actor