From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [RFCv3] Add message agent API
Date: Wed, 08 Sep 2010 16:04:47 +0200 [thread overview]
Message-ID: <1283954687.6640.35.camel@localhost.localdomain> (raw)
In-Reply-To: <1283949419-30222-1-git-send-email-aki.niemi@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
Hi Aki,
> + void RegisterAgent(object path, string type)
> +
> + Registers an agent to handle received messages.
> +
> + The object path defines the path of the agent that
> + will be called when a message is ready to be
> + dispatched. The type parameters accepts a MIME
> + type of the messages this agent is willing to
> + accept. Some common types include:
> +
> + "text/plain" - Regular text messages
> + "text/x-vcard" - vCard objects
> + "text/calendar" - vCalendar objects
> + "application/vnd.oma.push" - WAP push
> + "application/x-sms-agent" - Any datagram
> +
> + Wildcards are not allowed as the MIME subtype, but
> + registering an agent on a generic port is supported.
> + For instance, to listen on port 5678, the agent
> + would need to register using type:
> +
> + "application/x-sms-agent;port=5678"
so my obvious question here is, what kind of x-sms-agent type
applications do you expect? The need for text, vcard, vcalendar and push
messages is pretty clear. I still haven't figured out what other
applications are out there that we want do support with this. Can you
please give us some concert examples. I think that everybody else has
abandoned any other SMS message types.
Regards
Marcel
next prev parent reply other threads:[~2010-09-08 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 12:36 [RFCv3] Add message agent API Aki Niemi
2010-09-08 14:04 ` Marcel Holtmann [this message]
2010-09-08 15:39 ` Aki Niemi
2010-09-08 16:52 ` Marcel Holtmann
2010-09-08 17:57 ` Aki Niemi
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=1283954687.6640.35.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox