It sounds like a good idea, however its not entirely clear what would be
use of it. In the end user knows URI before hand, so he should be able
to process this information.
I agree that its better to normalize information on our end, but don't
see a clear use of it. With JDBC the connection metadata have a lot of
various elements, including product name, driver name, version and so on.
Best,
Łukasz
On 2/20/26 15:02, Christofer Dutz wrote:
Hi all,
I’m currently working on polishing the ManualDriverTest functionality and
wanted to output the name of the driver and the used transport name at the end
and noticed that we don’t expose that information.
I think this is not controversial … just wanted you to know that I’ll extend
the Metadata to include the protocol code, protocol name, transport code and
transport name in the PlcMetaData.
Hope you agree? (If not’s it’s easily revertible)
Chris
