Is your feature request related to a problem? Please describe.
This idea came up when thinking about how to implement messaging (ex. GroupMe) in Jablko without forcing a solution upon the user. Shifting the actual messaging implementation to be part of a JMOD would allow for Jablko to serve as a common interface between messaging JMODs.
Describe the solution you'd like
A JMOD can be installed that would take message data (say /sendMessage) and send it to some messaging service like GroupMe. On the admin panel, users would be able to select a JMOD (or JMODs) as an eligible client for messaging requests.
Describe alternatives you've considered
Hard coding a solution into Jablko goes against the general design I've been striving for. I would prefer to allow users full control over their system. Jablko should remain a common API for JMODs and handle security, authentication, and process manager.
Is your feature request related to a problem? Please describe. This idea came up when thinking about how to implement messaging (ex. GroupMe) in Jablko without forcing a solution upon the user. Shifting the actual messaging implementation to be part of a JMOD would allow for Jablko to serve as a common interface between messaging JMODs.
Describe the solution you'd like A JMOD can be installed that would take message data (say /sendMessage) and send it to some messaging service like GroupMe. On the admin panel, users would be able to select a JMOD (or JMODs) as an eligible client for messaging requests.
Describe alternatives you've considered Hard coding a solution into Jablko goes against the general design I've been striving for. I would prefer to allow users full control over their system. Jablko should remain a common API for JMODs and handle security, authentication, and process manager.