d when we refractor the scraper we just
> have to change all usages equally.
>
> Chris
>
> Von: Etienne Robinet <43...@etu.he2b.be>
> Gesendet: Freitag, 17. April 2020 20:27
> An: dev@plc4x.apache.org
> Betreff: Re: Camel Component feature
Hi Etienne,
Exactly ... Use the current api and when we refractor the scraper we just have
to change all usages equally.
Chris
Von: Etienne Robinet <43...@etu.he2b.be>
Gesendet: Freitag, 17. April 2020 20:27
An: dev@plc4x.apache.org
Betreff: Re: Camel Com
Hi Chris,
So what do tou think? Adapt the old scraper to use in the API and then use this
in the Camel component?
Etienne
> Le 17 avr. 2020 à 12:10, Christofer Dutz a écrit :
>
> Hi all,
>
> And we should really rewrite and clean up the scraper internally ;-)
>
> Still got that on my ToDo
Hi all,
And we should really rewrite and clean up the scraper internally ;-)
Still got that on my ToDo, but would be happy if someone would beat me to it ;-)
But I also agree that we shouldn't re-invent the wheel and reuse the components
we already have.
I think from an API side even a new sc
Etienne,
like so often you are absolutely right with your analysis oft he Situation : )
Indeed these are very valuable features.
In plc4x there exists a compontent called the "Scraper" (which I wrote
initially) and which was extended to a "TriggeredScraper" by @Tim Mitsch which
does exactly tha
Hi everyone,
As the Camel component is now working correctly, I thought about some features
we could add on it, based on work I read from a coworker. I would like to know
if these would fit inside this project and if so I would be glad to implement
them.
Trigger & Completion
To prevent writing
