Re: [DISCUSS] change connection string format

2019-07-16 Thread Julian Feinauer
Julian Feinauer Gesendet: Dienstag, 16. Juli 2019 09:05 An: Strljic, Matthias Milan ; dev@plc4x.apache.org Betreff: Re: [DISCUSS] change connection string format Hey Matthias, Personally, I feel that it would be better for users to keep fields "domain

Re: [DISCUSS] change connection string format

2019-07-16 Thread Christofer Dutz
close the contents to any other person. Thank you. -Ursprüngliche Nachricht- Von: Julian Feinauer Gesendet: Dienstag, 16. Juli 2019 09:05 An: Strljic, Matthias Milan ; dev@plc4x.apache.org Betreff: Re: [DISCUSS] change connection string format Hey Matthias, Personally, I feel that it w

Re: [DISCUSS] change connection string format

2019-07-16 Thread Julian Feinauer
Hey Matthias, Personally, I feel that it would be better for users to keep fields "domain" specific. At least I love that for S7 (and our users too). Perhaps we can introduce also a general unified language for that but optionally provide a specific one for each protocol. What do others think?

RE: [DISCUSS] change connection string format

2019-07-16 Thread Strljic, Matthias Milan
Hi Julian, I think that is a really good question. For the Connection String I would agree (+1) for your suggestion. But wanted to ask if there is a notation which is domain specific to a protocol from the "user" point of view? Like we have it in the FieldAddresses. So that we just throw into a

Re: [DISCUSS] change connection string format

2019-07-15 Thread Julian Feinauer
Hi Chris, sure, sorry for that. As some drivers have the possibility to add further configuration options I would like to unify that for all drivers. Camel uses the URI syntax for that, so e.g. for siemens one would write: s7://192.168.1.10?rack=0&slot=0 or, if both have a default value of 0 (w

Re: [DISCUSS] change connection string format

2019-07-15 Thread Christofer Dutz
Hi Julian, Could you post examples how the URLs would look like? Sorry, don't have the time to read the document you posted. So if you would post example strings for each driver type we currently have in plc4x, I think that would help us understand your proposal. Chris Holen Sie sichOutlook f