As you recall, I didn't object the changes in general. I just asked you to put them in a different layer oft he API. Right now, using only the PLC4X API there is no way a user could build the Field Objects. In order to do that he has to access types in a specific driver. This makes the application non-portable.
So What I could imagine would, be that if you have a connection, you ask for a "low-level-API" and this then allows to do stuff like your proposed change. Also perhaps stuff tools (Like NiFi, StreamPipes, etc.) could probably want/need in order to provide their services. I'd just like to keep the general API fool-proof, as we know that "fools" will also be using it. Chris -----Ursprüngliche Nachricht----- Von: Łukasz Dywicki <[email protected]> Gesendet: Donnerstag, 4. Februar 2021 23:26 An: [email protected] Betreff: Support for passing 'PlcField' intances to read/write/subscribe requests Hey, After processing some of PRs which didn't come into 0.8 I come to my own stuff which is intended to fix PLC4X-252. This change affects public API so it is worth to consider it early on with 0.9 just taking off. Code changes are rather small - https://github.com/apache/plc4x/pull/201 I have ongoing discussion with Chris about it how this change should be integrated into code base. I would welcome input from others so we get into consensus there. Whole point is to let user pass field instance without invocation of FieldHandler which is there to parse String into PlcField. Some of pros/cons are outlined in comments under PR. Looking forward to your input. Best, Łukasz
