Is there any reason why NetConnection.SendConnectReponse doesn't use
m_remoteUniqueIdentifier in the response for a better handshake check ?
internal void SendConnectResponse()
{
...
reply.Write(m_remoteUniqueIdentifier);
..
}
And then check in the NetPeer.Internal when ConnectResponse comes not only for
sender but with the uniqueId too.
Also NetConnection.m_remoteUniqueIdentifier is initialized only in server side
when NetMessageLibraryType.Connect message is received but not for client side
in Connect method.
NetPeer.Connect method can initialize NetConnection:
public virtual NetConnection Connect(...)
{
...
conn.m_remoteUniqueIdentifier = m_uniqueIdentifier;
m_connections.Add(conn);
...
}
Otherwise I don't see the need of unique identifier in the connection.
Original issue reported on code.google.com by NN1436...@gmail.com on 17 Aug 2010 at 1:42
Original issue reported on code.google.com by
NN1436...@gmail.com
on 17 Aug 2010 at 1:42