Morning! So I think if we make a clear concept and just reqrite it, it should > be pretty easy and get more robust. > Under the hood its not much more than a Connection Pool and a > ScheduledExecutor, right?
Any place where I can read what the Scraper goals are apart from reading the code? From this comment, I imagine that it is a tool to collect the data from different PLCs in a scheduled way. Cheers! > > Best! > Julian > > Am 12.01.20, 13:32 schrieb "Lukas Ott" <ott.lukas...@gmail.com>: > > Hi, > > +1 for rewriting the scraper. In my humble opinion the PLC4X > project still > aims for multiple language support and the scraper including the > integration into calcite, kafka and logstash are core > capabilities that > should be supported. > > Lukas > > Am So., 12. Jan. 2020 um 12:51 Uhr schrieb Christofer Dutz < > christofer.d...@c-ware.de>: > > > Hi all, > > > > for about 7 full days have I been cleaning up the new branch in > order to > > port all the other drivers besides the S7 to the new API … > > This forced me to go through about all modules we have. > > > > One module that however causes me to worry is the scraper. It’s > a core > > module we use in the calcite-integration, kafka-connect and the > logstash > > module. > > The last two ones are some that are gaining pretty much > traction. > > > > However I feel very uncomfortable having dug into the current > scraper … so > > I would propose to completely rewrite it. I tried refactoring > it for 1,5 > > days and just recently simply reverted my changes … currently > I’m just > > trying to get things to build again. > > > > As Julian told me he and his company have sort of moved away > from the > > scraper to something new … I would like to discuss the > alternatives with > > you. > > > > Right now for me it feels impossible to provide support if > anything goes > > wrong in the scraper. > > > > Chris > > > > > > > >
