Well, in general I meant the user-facing things. Hence the naming of the modules in the extensions repo with adapters - but also the naming of the Docker container. This is currently also referred to as „worker-main“.
In a second step however, it also makes sense to apply this to the backend modules. If its better to have the notion of „worker“ somewhere inside the naming scheme it should be clear and in both backend and extensions. I am more in favor of having it clean and I guess adapters are more common as this is what we talk about most of the time anyways :) But maybe you have a better idea? Patrick > Am 06.10.2021 um 10:28 schrieb Philipp Zehnder <[email protected]>: > > Hi Patrick, > > I totally agree, we should harmonize the naming. > But what are you referring to? To the naming of the modules of the connect > adapters in the worker or the modules in the backend? > > My suggestion for the modules containing the adapters would be: > streampipes-connect-adapters and streampipes-connect-adapters-iiot > Do you have an alternative suggestion? > > Philipp > > >> On 6. Oct 2021, at 10:15, Patrick Wiener <[email protected]> wrote: >> >> Hi, >> >> fine for me. But when refactoring, would it make sense to also align the >> naming because >> it might be not to intuitive having „workers“ denoting the architectural >> paradigm and „adapters“ >> for the protocols. >> >> Pipeline element services act similarly but aren’t referred to as „workers“ >> for pipeline elements too. >> >> What do you think about that as there is already some refactoring going on? >> >> Patrick >> >>> Am 06.10.2021 um 09:45 schrieb Philipp Zehnder <[email protected]>: >>> >>> Hi Dominik, >>> >>> that is fine with me +1 >>> >>> Philipp >>> >>>> On 6. Oct 2021, at 09:43, Dominik Riemer <[email protected]> wrote: >>>> >>>> Hi Philipp, >>>> >>>> I'd propose to also move the InfluxDB, Netio and Pulsar adapters to the >>>> iiot >>>> module. >>>> Reason is that these are also "enterprise-grade" adapters that might be >>>> useful for IIOT applications, so that users can deploy a single module and >>>> find all potentially relevant adapters for their industry. >>>> >>>> What do you think? >>>> >>>> Dominik >>>> >>>> -----Original Message----- >>>> From: Philipp Zehnder <[email protected]> >>>> Sent: Wednesday, October 6, 2021 8:57 AM >>>> To: [email protected] >>>> Subject: Re: [DISCUSS] Split StreamPipes Connect worker >>>> >>>> Hi, >>>> >>>> the idea of the issue is to split up the package >>>> streampipes-connect-adapters into two packages, one containing only the >>>> relevant adapters for IIoT scenarios and one with others. >>>> So the next step would be to create a new module, add all the adapters >>>> there, as listed below. As a template you can use the already existing >>>> module. >>>> >>>> >>>> * streampipes-connect-adapters >>>> * GdeltAdapter >>>> * CoindeskBitcoinAdapter >>>> * IexCloudNewsAdapter >>>> * IexCloudStockAdapter >>>> * RandomDataSetAdapter >>>> * RandomDataStreamAdapter >>>> * SlackAdapter >>>> * WikipediaEditedArticlesAdapter >>>> * WikipediaNewArticlesAdapter >>>> * InfluxDbStreamAdapter >>>> * InfluxDbSetAdapter >>>> * NetioRestAdapter >>>> * NetioMQTTAdapter >>>> * ImageStreamAdapter >>>> * ImageSetAdapter >>>> * IssAdapter >>>> * FlicMQTTAdapter >>>> * HDFSProtocol >>>> * PulsarProtocol >>>> >>>> * streampipes-connect-adapters-iiot >>>> * MySqlStreamAdapter >>>> * MySqlSetAdapter >>>> * MachineDataStreamAdapter >>>> * RosBridgeAdapter >>>> * OpcUaAdapter >>>> * Plc4xS7Adapter >>>> * Plc4xModbusAdapter >>>> * FileProtocol >>>> * HttpProtocol >>>> * FileStreamProtocol >>>> * KafkaProtocol >>>> * MqttProtocol >>>> * HttpStreamProtocol >>>> * HttpServerProtocol >>>> >>>> Write me if something is unclear. >>>> >>>> Philipp >>>> >>>>> On 5. Oct 2021, at 15:37, hrushi <[email protected]> wrote: >>>>> >>>>> Hi >>>>> >>>>> I would like to contribute and fix this issue. I would like to know the >>>> prerequisites for this issue so that I can go through those concepts. New >>>> to >>>> open source and will try to contribute. >>>>> >>>>> Thank You. >>>>> >>>> >>>> >>> >> >
