04-06-2021, 03:42 PM
(This post was last modified: 04-06-2021, 03:45 PM by bitsandnumbers.)
(04-06-2021, 09:30 AM)blendergeek Wrote:(04-05-2021, 07:52 PM)kop316 Wrote: I was additionally wondering if I do Issue 6, then does it make sense to then bake in SMS functionality as well (Issue 7). I am not convinced I should do that. Right now I am thinking mmsd should only focus on MMS (it is called mmsd afterall), and SMS sending/recieving is much more straight forward with modem manager. But, I figured I should write it down and think about it anyways. If I did add it, it would be a user option as well.
Ideally, in my mind, this is how it _should_ work. There should be one "mms-smsd". Every application that wants to send a "message" should go through the one daemon. This way, applications will neither know nor care whether it is an SMS or an MMS. The application just passes the message to mmsd and mmsd figures out how to send it.
Eventually, mmsd will support RCS as well in my fantasies ...
I don't understand everything about your work here @kop316 , but as an adept of the KISS principle, I can only adhere to what @blendergeek is suggesting. One could argue that KISS would be having one daemon doing one thing and doing it good, but MMS/SMS are pretty much the same thing, one being just richer than the other (at least from an end-user POV, also when you use SMS/MMS, you usually use the other), so one daemon managing both does not bother me here. And it would also save nights for future devs wanting to make SMS/MMS clients I assume... I'm not technical on the matter though, so I'm just giving my Linux user opinion.
