General information regarding using plugins
-
Hello All,
I have various classes like camera,serialport etc.
Is it good idea to create a separate plugins for those classes ?
Also in the production enviroment ( software release) do we have to provide the
plugins(dll ) separately?
Is there any security concern related to it -
Hello All,
I have various classes like camera,serialport etc.
Is it good idea to create a separate plugins for those classes ?
Also in the production enviroment ( software release) do we have to provide the
plugins(dll ) separately?
Is there any security concern related to it@Kira said in General information regarding using plugins:
Is it good idea to create a separate plugins for those classes ?
(personal opinion) I don't think so. Plugins are fine for cases where you need to dynamically support some functionality - distribute one application where users can extend the functionality by enabling / disabling plugins. Like in Qt Creator, you can have extra options added by some plugins.
A plugin layer adds a lot of complexity to a project, though, and (in Qt) plugins often need to be recompiled for every new release, and you need to keep the plugin API stable etc. It's a lot of additional work.
It is a good idea to keep such functionality (camera, etc.) separate, but that can be done using a library, or even well-designed classes that don't get entangled.
Also in the production enviroment ( software release) do we have to provide the plugins(dll ) separately?
You can bundle them inside the installer, if that's what you mean.
Is there any security concern related to it
Yes. Somebody can take your DLL or plugin DLL and create their own, malicious version of it. Then they could use that to access some private data, customer credentials, or even gain access to user's PC.
(Z(:^
-
@Kira said in General information regarding using plugins:
Is it good idea to create a separate plugins for those classes ?
(personal opinion) I don't think so. Plugins are fine for cases where you need to dynamically support some functionality - distribute one application where users can extend the functionality by enabling / disabling plugins. Like in Qt Creator, you can have extra options added by some plugins.
A plugin layer adds a lot of complexity to a project, though, and (in Qt) plugins often need to be recompiled for every new release, and you need to keep the plugin API stable etc. It's a lot of additional work.
It is a good idea to keep such functionality (camera, etc.) separate, but that can be done using a library, or even well-designed classes that don't get entangled.
Also in the production enviroment ( software release) do we have to provide the plugins(dll ) separately?
You can bundle them inside the installer, if that's what you mean.
Is there any security concern related to it
Yes. Somebody can take your DLL or plugin DLL and create their own, malicious version of it. Then they could use that to access some private data, customer credentials, or even gain access to user's PC.
