Betreff: Re: AW: Source Time of PLC Value?
Hey Matthias and Chris,
I agree with you about complexity and alignment. I am far from trying to cover
each and every case. At the same time I am aware that making thing fine in
first run is crucial to avoid major changes afterwards. That's also why I did
On Thu, 2021-03-11 at 19:13 +0100, Łukasz Dywicki wrote:
> [snip] ..
> While I do appreciate work made to bring all (C/Python/C#?) languages
> under Apache PLC4X umbrella I also do see that sometimes they are
> being
> {snip]
> Isn't it a time to make sure that C/C#/Python can still compile with
eb Christofer Dutz <
>>> christofer.d...@c-ware.de>:
>>>
>>>> Hi,
>>>>
>>>> I'm generally more concerned about users expecting us to deliver feature
>>>> that driver X has for driver Y too.
>>>>
>>>> I won'
er X has for driver Y too.
> >>
> >> I won't object, if you think it's worth doing.
> >>
> >> Perhaps if you could whip up an example in a feature branch? I think
> >> perhaps I was still not understanding what you propose.
> >>
> >>
, not make
things too complicated for normal users or to have a significant impact on
performance.
Chris
-Ursprüngliche Nachricht-
Von: Łukasz Dywicki
Gesendet: Mittwoch, 10. März 2021 17:28
An: dev@plc4x.apache.org
Betreff: Re: AW: AW: AW: Source Time of PLC Value?
On technical side
to
> open terminals on PLCs and execute arbitrary code on the remote device. Cause
> this is all stuff I have been doing using JDBC ;-)
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Łukasz Dywicki
> Gesendet: Mittwoch, 10. März 2021 15:05
> An: dev@plc4x.apac
C4X to
> open terminals on PLCs and execute arbitrary code on the remote device. Cause
> this is all stuff I have been doing using JDBC ;-)
>
> Chris
>
>
> -Ursprüngliche Nachricht-----
> Von: Łukasz Dywicki
> Gesendet: Mittwoch, 10. März 2021 15:05
> An: dev@
all of this and it seems to be gaining
>> more and more traction, just because it doesn't have all of this overhead.
>>
>> Just my thoughts on this.
>>
>> Chris
>>
>>
>>
>>
>> -Ursprüngliche Nachricht-
>> Von: Łukasz D
> Gesendet: Mittwoch, 10. März 2021 12:58
> An: dev@plc4x.apache.org
> Betreff: Re: AW: Source Time of PLC Value?
>
> Matthias,
> I do believe there are several points which are relevant and still not
> possible to be implemented using available PLC4X API. Metadata mi
2021 15:05
An: dev@plc4x.apache.org
Betreff: Re: AW: AW: Source Time of PLC Value?
Chris,
What we discuss is whether there is a need and use for result set metadata or
not. Given initial statement of "being a for of JDBC for industrial devices"
and looking at JDBC itself we should provid
of this and it seems to be gaining
> more and more traction, just because it doesn't have all of this overhead.
>
> Just my thoughts on this.
>
> Chris
>
>
>
>
> -Ursprüngliche Nachricht-
> Von: Łukasz Dywicki
> Gesendet: Mittwoch, 10. März 2021 12:58
@plc4x.apache.org
Betreff: Re: AW: Source Time of PLC Value?
Matthias,
I do believe there are several points which are relevant and still not possible
to be implemented using available PLC4X API. Metadata might not be most
fortunate way, but it can enable or ease analytical and troubleshooting
scenarios.
Two
n't object, if you think it's worth doing.
>>
>> Perhaps if you could whip up an example in a feature branch? I think
>> perhaps I was still not understanding what you propose.
>>
>> Would that be ok?
>>
>>
>> Chris
>>
>>
>> -Ursprüngliche
>>
>> Would that be ok?
>>
>>
>> Chris
>>
>>
>> -Ursprüngliche Nachricht-
>> Von: Lukas Ott
>> Gesendet: Montag, 8. März 2021 14:20
>> An: dev@plc4x.apache.org
>> Betreff: Re: AW: Source Time of PLC Value?
>>
>&
was still not understanding what you propose.
>
> Would that be ok?
>
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Lukas Ott
> Gesendet: Montag, 8. März 2021 14:20
> An: dev@plc4x.apache.org
> Betreff: Re: AW: Source Time of PLC Value?
>
> +1 t
that be ok?
Chris
-Ursprüngliche Nachricht-
Von: Lukas Ott
Gesendet: Montag, 8. März 2021 14:20
An: dev@plc4x.apache.org
Betreff: Re: AW: Source Time of PLC Value?
+1 to Lukasz
Am Mo., 8. März 2021 um 14:09 Uhr schrieb Łukasz Dywicki <
l...@code-house.org>:
> Hold on for
+1 to Lukasz
Am Mo., 8. März 2021 um 14:09 Uhr schrieb Łukasz Dywicki <
l...@code-house.org>:
> Hold on for a second.
>
> Making options pushed over connection string is a long term recipe for
> disaster. Apache Camel is a prime example of what could happen if you
> starting with configuration
Hold on for a second.
Making options pushed over connection string is a long term recipe for
disaster. Apache Camel is a prime example of what could happen if you
starting with configuration with URIs and dynamic parameters. Most of
components distinguish producer (writer) and consumer (receiver)
Hi,
I must admit that I would be in favor of keeping it as simple as possible (max
age in the connection string) and to implement more of the missing parts in
plc4x (like the subscription simulation layer) and hereby getting the drivers
we have a bit more aligned, than to implement more and
Hi all,
sorry for being late to the party ... KNX is currently consuming all my cycles.
Just wanted to add my thoughts to the discussion.
Initially I thought about adding this sort of information to the API, but then
I thought that we have so little protocols supporting this sort of concept
This is not a simple questing and depends on the protocol and device you are
using. What are you using?
J
Von meinem Mobiltelefon gesendet
Ursprüngliche Nachricht
Von: Andreas Vogler
Datum: Fr., 5. März 2021, 21:04
An: dev@plc4x.apache.org
Betreff: Re: Source Time of PLC
21 matches
Mail list logo
