Describe the bug
The IEC104 Server won't call the Connection Handler for the OPENED and Active ConnectionStates any more in the 2.3.0 release
To Reproduce
Register
server.SetConnectionEventHandler(handler, null);
Usage
private void handler(object parameter, ClientConnection connection, ClientConnectionEvent eventType)
{
logger.LogInformation("connection event ({type}): {adress}", eventType.ToString(), connection.RemoteEndpoint.Address.ToString());
if (eventType == ClientConnectionEvent.OPENED)
{ //NOT FIRED ANYMORE
_connected = true;
}
else if (eventType == ClientConnectionEvent.ACTIVE)
{ //NOT FIRED ANYMORE
}
else if (eventType == ClientConnectionEvent.CLOSED)
{ //STILL WORKS
_connected = false;
}
}
Expected behavior
The handler worked in 2.2.0. If there is a IEC104 Client connecting to the server i can find out if some client is still connected.
Priority
This is important but not urgent as nobody is forced to update.
Container
-
OS: Windows/Linux
-
Version Windows 11
-
.NET Version: 10.0
Additional context
Client is using the same library and is already on version 2.3.0
Describe the bug
The IEC104 Server won't call the Connection Handler for the OPENED and Active ConnectionStates any more in the 2.3.0 release
To Reproduce
Register
Usage
Expected behavior
The handler worked in 2.2.0. If there is a IEC104 Client connecting to the server i can find out if some client is still connected.
Priority
This is important but not urgent as nobody is forced to update.
Container
OS: Windows/Linux
Version Windows 11
.NET Version: 10.0
Additional context
Client is using the same library and is already on version 2.3.0