Hi, as announced in my last mail, I'm here to work with + improve ofono and related software. My next task will be to implement an ofono plugin which handles some UPL push messages. Because there is only one "listener" at org.ofono.PushNotificationAgent possible, I see two and a half way to go on: 1) fork ofono-mmsd to handle more message types than mms (via plugins?) 1b) fork ofono-mmsd to handle only SUPL push messages 2) find a way for more listeners on push messages Any suggestions, preferred ways? Best regards and have a nice weekend, Jens

>> as announced in my last mail, I'm here to work with + improve ofono >> and related software. >> >> My next task will be to implement an ofono plugin which handles some >> UPL push messages. Because there is only one "listener" at >> org.ofono.PushNotificationAgent possible, I see two and a half way >> to go on: >> >> 1) fork ofono-mmsd to handle more message types than mms >> (via plugins?) >> 1b) fork ofono-mmsd to handle only SUPL push messages >> 2) find a way for more listeners on push messages >> >> Any suggestions, preferred ways? > > I think there is a third way to do what you want : write a SUPL push > message consumer as an mmsd plugin and not as an ofono plugin. Actually, > mmsd already implements a WAP push message dispatch mechanism for other > push message than MMS. > To check if this fits your needs, please have a look at the consumer.txt > documentation from mmsd/doc/. Yeah, you're right. I read it on my first day and had it totally forgotten meanwhile. Initially it confuses me, because I assumed there can be embedded documents in an mms - and didn't recognize that mms is the built-in plugin for mmsd - which should be renamed into wspd ;)