I added that cause as soon as you don't communicate with only one type of source I had to work with full package names multiple times now. With the PLC prefix to make the domain clear. Just imagine having a Kafka connection, DB connection, whatever connection. Most people stripped prefixes from their types ... So you end with multiple "Connection" classes.
Chris Outlook for Android<https://aka.ms/ghei36> herunterladen ________________________________ From: Julian Feinauer <[email protected]> Sent: Monday, October 8, 2018 1:50:16 PM To: [email protected] Subject: Re: Plc Prefix on all API Types Hi Andrey, this was my first thought also. But now I'm unsure whether this si a problem or not as it makes it really clear when working with PlC4X related stuff and when not. And it avoids confusion with wrong imports when typing something like "ReadReq..." (auto-complete) which is about the most annoying "bug" you can have. +0 from my side. Julian Am 08.10.18, 12:42 schrieb "Andrey Skorikov" <[email protected]>: Hello all, currently all types in the API module begin with the "Plc" prefix. I think that this adds unnecessary noise to the API, since these types reside in a separate Java package anyway, and therefore a separate namespace, so name collisions are avoided. Perhaps we can get rid of this prefix? What do others think? Andrey
