dorkbox/Network
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fixed thread visibility issues in the client handshake when reconnecting

Browse Source
This commit is contained in:
nathan 2020-09-10 14:38:54 +02:00
parent c13fb205cf
commit 7db6a45437
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/dorkbox/network/handshake/ClientHandshake.kt
View File

@ -25,16 +25,19 @@ import dorkbox.network.exceptions.ClientTimedOutException
import io.aeron.FragmentAssembler
import io.aeron.logbuffer.FragmentHandler
import io.aeron.logbuffer.Header
import mu.KLogger
import org.agrona.DirectBuffer
import java.security.SecureRandom
internal class ClientHandshake<CONNECTION: Connection>(private val logger: KLogger,
private val config: Configuration,
internal class ClientHandshake<CONNECTION: Connection>(private val config: Configuration,
private val crypto: CryptoManagement,
private val endPoint: EndPoint<CONNECTION>) {
// @Volatile is used BECAUSE suspension of coroutines can continue on a DIFFERENT thread. We want to make sure that thread visibility is
// correct when this happens. There are no race-conditions to be wary of.
// a one-time key for connecting
private val oneTimePad = SecureRandom().nextInt()
private val handler: FragmentHandler
@Volatile
private var connectionHelloInfo: ClientConnectionInfo? = null
@ -45,7 +48,7 @@ internal class ClientHandshake<CONNECTION: Connection>(private val logger: KLogg
@Volatile
private var failed: Exception? = null
private var handler: FragmentHandler
@Volatile
private var sessionId: Int = 0
init {