I need an clarification and/or have request for change in our API/SPI. This is closely related to further CAN bus work I plan to do, but not only. I do see that what Ben did few weeks ago with connection tracking is very interesting to move forward. At present we do not offer end user an API to react on connection shutdown or failure. There is no way for him to find that ie. link died and his program needs to take action.
What I currently also do not understand/lack clearance is how stack configurer interacts with TCP connection. Here what bothers me: - Is there a new stack/decode instance per each active connection? - What is was intended design for driver context and why it is inaccessible via PLC connection interface? I suppose that stack per connection is desired case, but if that's true why we pass classes and instead of creating instances in stack configurer? My case here is intended to attach connection state listener but also an message listeners which could help debugging message exchanges. All without tapping into wire. A default way we advertise is making PCAP recordings which is fine for development. What I look for is an "logging" interface to be used in production or test environments without necessity to get libpcap involved. This would allow creation of additional tools if needed. Best, Łukasz
