All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Rehsack <jr_extern@vfnet.de>
To: ofono@ofono.org
Subject: Re: Enhancing mmsd
Date: Fri, 24 Feb 2012 16:17:13 +0100	[thread overview]
Message-ID: <4F47A9F9.7010407@vfnet.de> (raw)
In-Reply-To: <4F47A235.40807@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]

Am 24.02.2012 15:44, schrieb Ronald Tessier:
> Hi Jens,
> 
> On 02/24/2012 02:29 PM, Jens Rehsack wrote:
>> 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?
> 
> 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 ;)

So my proposal 1 is already done - but I was to much confused to
recognize it. Thanks to point me on it.

Best regards,
Jens

  reply	other threads:[~2012-02-24 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 13:29 Enhancing mmsd Jens Rehsack
2012-02-24 14:44 ` Ronald Tessier
2012-02-24 15:17   ` Jens Rehsack [this message]
2012-02-27  2:14     ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F47A9F9.7010407@vfnet.de \
    --to=jr_extern@vfnet.de \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.