Hmmm ... I just stumbled over a sort of slightly annoying problem.
This currently only is a problem in the Go version of the KNX driver, as this is the only with an implemented Browse functionality. The Browse operation is related to a connection and therefore you run it on a connection object. Now the problem is: As soon as you start using a connection pool, and run the Browse operation, this takes long (Several minutes and longer the more devices are there). This now exceeds the normal lease-time of a pooled connection. However internally the Browse operation mostly uses the connection to execute simple plc4x operations ... so in general it would work to give back the connection after each operation. But as the browse operation is part of the connection, this doesn't work. I think this will be a problem that we'll be having with other drivers too. So possibly it would make sense to not locate the Browse functionality in the connection, but outside and have it simply use a connection. Not 100% sure how this would look like ... I'm totally open for suggestions here ;-) Chris
