(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 ...
> mmsd will support RCS as well in my fantasies ...
Do you have any knowledge of where to look for a reference on this? It would be interesting to see how RCS works,
https://www.gsma.com/futurenetworks/rcs/ seem to be the ultimate authority on it, with this document specifying clients:
https://www.gsma.com/futurenetworks/wp-c...-v11.0.pdf
but it would be easier to look at reference code. The Google messaging RCS is proprietary as far as I can tell. Also as a note:
"Operators are free to decide whether or not to implement RCS within their 4G networks. However, the 5G standards mandate the implementation of RCS in 5G networks and devices."
https://www.gsma.com/futurenetworks/rcs/...l-profile/
It looks like if one were to impliment 5G, one needs RCS.
