From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 2/3] doc: Describe delivered group in storage doc
Date: Thu, 07 Jun 2012 11:43:21 +0900 [thread overview]
Message-ID: <1339037001.1817.120.camel@aeonflux> (raw)
In-Reply-To: <1338454376-12806-3-git-send-email-ronald.tessier@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]
Hi Ronald,
> doc/storage.txt | 30 ++++++++++++++++++++++++++++++
> 1 files changed, 30 insertions(+), 0 deletions(-)
>
> diff --git a/doc/storage.txt b/doc/storage.txt
> index 8e76382..0aa6d9d 100644
> --- a/doc/storage.txt
> +++ b/doc/storage.txt
> @@ -18,6 +18,7 @@ Meta file Example
> [info]
> read=false
> state=notification
> +message_id=0123456789ABCDEF
I would just shortcut this to "id". Or is the a reason to keep
"message_id" for this?
> Meta file Keys/Values details
> @@ -31,3 +32,32 @@ state: The message local state, possible values can be:
> - "received": m-Retrieve.Conf PDU downloaded and successfully acknowledged.
> - "draft": m-Send.Req PDU ready for sending.
> - "sent": m-Send.Req PDU successfully sent.
> +
> +message_id: this is the value provided in the M-Send.conf PDU (assigned by MMSC
> +in response to a M-Send.req message), this entry will only be created upon
> +M-Send.conf message reception if the delivery report was requested.
> +
> +For sent messages, a group [delivery_status] could take place in addition to
> +[info] if delivery report is requested.
> +In this group, every recipient has a MMS Delivery status value which can be one
> +of the following:
> + - "none": no report has been received yet.
> + - "expired": recipient did not retrieve the MMS before expiration.
> + - "retrieved": MMS successfully retrieved by the recipient.
> + - "rejected": recipient rejected the MMS.
> + - "deferred": recipient decided to retrieve the MMS at a later time.
> + - "indeterminate": cannot determine if the MMS reached its destination.
> + - "forwarded": recipient forwarded the MMS without retrieving it first.
> + - "unreachable": recipient is not reachable.
> +
> +
> +Example of a sent_message meta file with delivery report requested
> +==================================================================
> +
> +[info]
> +state=sent
> +message_id=0123456789ABCDEF
> +
> +[delivery_status]
> +21345=retrieved
> +09876=none
How is this suppose to work. I am kinda failing to see what this tries
to solve.
Regards
Marcel
next prev parent reply other threads:[~2012-06-07 2:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 8:52 [PATCH 0/3] mmsd: (resending) new tasks definition Ronald Tessier
2012-05-31 8:52 ` [PATCH 1/3] TODO: Add new tasks Ronald Tessier
2012-06-07 2:43 ` Marcel Holtmann
2012-05-31 8:52 ` [PATCH 2/3] doc: Describe delivered group in storage doc Ronald Tessier
2012-06-07 2:43 ` Marcel Holtmann [this message]
2012-06-07 14:33 ` Ronald Tessier
2012-05-31 8:52 ` [PATCH 3/3] doc: Add new D-Bus methods to service interface Ronald Tessier
2012-06-07 2:43 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2012-05-22 13:57 [PATCH 0/3] mmsd: new tasks definition Ronald Tessier
2012-05-22 13:58 ` [PATCH 2/3] doc: Describe delivered group in storage doc Ronald Tessier
2012-05-21 15:59 [PATCH 0/3] mmsd: new tasks definition Ronald Tessier
2012-05-21 15:59 ` [PATCH 2/3] doc: Describe delivered group in storage doc Ronald Tessier
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=1339037001.1817.120.camel@aeonflux \
--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