Hi Ruwan,
We have included the notification providers like GCM, MQTT, FireBase inside
the core (in device-mgt-extensions component) in the existing
implementation of device-mgt. I do agree with your comment that says those
are only extensions to the core framework. Have we thought of moving them
o
@Dilan,
The idea here is that things like the transports adapters and the
appm-connector are modular plugins that are just complementing the CDMF
which is s framework. The framework does not necessarily need these to
function and perform its core tasks. Hence these should evolve/get added
independe
Hi Ruwan,
How about having a UI for the plugin deployment? So plugins can be
installed and uninstalled via the UI like how we install/uninstall features
in the carbon console.
On Tue, Nov 22, 2016 at 9:59 PM, Dilan Udara Ariyaratne
wrote:
> Hi Ruwan,
>
> Why would not analytics be inside a part
Hi Ruwan,
Why would not analytics be inside a particular device type ?, this is in
fact the idea provided in [1].
And also, if these Input/Output transport adapters and extensions for
MB/APP-M are in common to any device type,
cannot we move them down to carbon-device-mgt platform layer ?
Referen
Hi All,
In line with the changes that have been done to introduce the device-type
descriptor in [1], I have gone ahead and done some refactoring to the
existing plugins to standardise + make them self-contained. Following are a
list of changes introduced.
- Mobile Base plugin is no more :
