luca-domenichini / smartiot.connector Goto Github PK

as of 2024-01-10 we have a warning in github actions:

see https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Would be good to have grpc connectors, both client and server style.

Server connector should bring up a grpc service that allows clients to request data on demand.
It should also provide a streaming method to have events pushed to clients asynchronously.
This package (or another one?) should also provide a client library to be easily used by external processes

Client connector should do the same but the opposite way.
This package (or another one?) should also provide a grpc service to be installed in an external application that wants to act as the grpc service server. External clients, at this point, should query that grpc service for data/status/streaming etc...

Maybe client and server packages can be the same in both connector kind, be that SmartIOT -> grpc client -> grpc server or SmartIOT -> grpc server -> grpc client... maybe some endpoints would be useless.. must investigate that.

Reduce memory allocation on read/write operations.
The goal is to use the underlying byte[] as source or target directly, without further allocations.

• use existing Span aware methods on S7Net
• introduce new method Span aware on Snap7 and SnapModBus

The proto files should be part of SmartIOT.Connector.Messages project

Docs for how to easily create a customized device and connector is missing.
People now should simply copy from existing implementations.

Would be good to have a web app integrated in the default app to display some data about the internals of the running system.

That app should use the API already exposed to display statistics, and should also provide a way to update the system state:

• add/remove device
• add/remove connector
• get data, set data
• etc...

Build and push docker image with github workflow

Introduce IAsyncDeviceDriver and add support to autodiscover and run them