splatch commented on issue #1407: URL: https://github.com/apache/plc4x/issues/1407#issuecomment-2052169595
The historic context of this connection is fairly basic: 1) User application has no ways to determine state of connection, we internally process connected/disconnected events, but user never actually knows if connection was terminated by remote until it gets an error. Getting a `ConnectionListener` allows to track lifecycle of connection and act accordingly. 2) There is no way to simplify track low level traffic other than tapping a wireshark, which can be troublesome under production environments. Possibility to attach `MessageExchangeListener` provides interception point for user application to get messages in raw form. That's whole motivation of it. Given that our API didn't have above concepts they were built as a supplement with this extra interface. It would be ideal if they could travel to the SPI. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
