Moved secure cookie exchange to on connect established, this means I could remove the synchronization on send, enabling muuuch more throughput, also, since the cookie isn`t sent in each message, message size should drop considerably when secure cookie handshakes are enabled. I do however have no way of testing this since it seems like the clustering stuff is totally not working when it comes to the RemoteSupport
This commit is contained in:
parent
b9a1d49999
commit
41a08237d9
4 changed files with 100 additions and 132 deletions
|
|
@ -78,10 +78,9 @@ object ActorSerialization {
|
|||
actorRef.timeout,
|
||||
Right(m.message),
|
||||
false,
|
||||
actorRef.getSender,
|
||||
RemoteClientSettings.SECURE_COOKIE).build)
|
||||
actorRef.getSender))
|
||||
|
||||
requestProtocols.foreach(rp ⇒ builder.addMessages(rp))
|
||||
requestProtocols.foreach(builder.addMessages(_))
|
||||
}
|
||||
|
||||
actorRef.receiveTimeout.foreach(builder.setReceiveTimeout(_))
|
||||
|
|
@ -201,8 +200,7 @@ object RemoteActorSerialization {
|
|||
timeout: Long,
|
||||
message: Either[Throwable, Any],
|
||||
isOneWay: Boolean,
|
||||
senderOption: Option[ActorRef],
|
||||
secureCookie: Option[String]): RemoteMessageProtocol.Builder = {
|
||||
senderOption: Option[ActorRef]): RemoteMessageProtocol.Builder = {
|
||||
|
||||
val uuidProtocol = replyUuid match {
|
||||
case Left(uid) ⇒ UuidProtocol.newBuilder.setHigh(uid.getTime).setLow(uid.getClockSeqAndNode).build
|
||||
|
|
@ -238,8 +236,6 @@ object RemoteActorSerialization {
|
|||
case s ⇒ s
|
||||
}
|
||||
|
||||
secureCookie.foreach(messageBuilder.setCookie(_))
|
||||
|
||||
/* TODO invent new supervision strategy
|
||||
actorRef.foreach { ref =>
|
||||
ref.registerSupervisorAsRemoteActor.foreach { id =>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue