From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [RFC 2/2] doc: Add description for history agent interface
Date: Fri, 04 Feb 2011 13:01:18 -0600 [thread overview]
Message-ID: <4D4C4CFE.3010508@gmail.com> (raw)
In-Reply-To: <A459777776EB4841B844E1134E7928740157C9DC@008-AM1MPN1-016.mgdnok.nokia.com>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
Hi Mikhail,
On 02/04/2011 12:52 PM, mikhail.zabaluev(a)nokia.com wrote:
> Hi,
>
>> -----Original Message-----
>> From: ofono-bounces(a)ofono.org [mailto:ofono-bounces(a)ofono.org] On
>> Behalf Of ext Marcel Holtmann
>> Sent: Friday, February 04, 2011 8:13 PM
>> To: ofono(a)ofono.org
>> Subject: RE: [RFC 2/2] doc: Add description for history agent interface
>>
>>> Why, you already cache fragments by their respective message refs
>> efficiently.
>>> The only thing missing is a thin API to provide a view on complete
>> messages.
>>
>> we are not storing the complete message. We give it to the history API.
>
> Somehow we never got to the "because" part in this discussion. Or is it a dogma in oFono?
>
Because we wanted to avoid this exact discussion. If you want some
particular API for text messaging, feel free to implement it.
Everything you need is provided. The sms assembly / status assembly
code will not help you in any way here.
>
> Sorry, I only jumped into the discussion after it has started and did not read the patch.
> But now that I do, I see an additional AddMatch and a GetOwnerName in this flow.
>
> And the failure mode of the agent disconnecting is... to drop events on the floor???
>
Then please take the hint and get more background first. Marcel did
mention in the thread that his patch is an RFC (he is a maintainer after
all) and that spooling of messages when the agent is not registered is
still not done.
Regards,
-Denis
next prev parent reply other threads:[~2011-02-04 19:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 17:29 [RFC 2/2] doc: Add description for history agent interface Marcel Holtmann
2011-02-02 13:23 ` Kai.Vehmanen
2011-02-02 16:43 ` Marcel Holtmann
2011-02-02 18:14 ` mikhail.zabaluev
2011-02-02 19:22 ` Denis Kenzior
2011-02-02 22:56 ` Kai.Vehmanen
2011-02-02 23:12 ` Marcel Holtmann
2011-02-03 10:54 ` mikhail.zabaluev
2011-02-03 7:13 ` Denis Kenzior
2011-02-03 10:11 ` Kai.Vehmanen
2011-02-03 12:42 ` mikhail.zabaluev
2011-02-03 11:57 ` mikhail.zabaluev
2011-02-03 15:58 ` Denis Kenzior
2011-02-02 19:32 ` Marcel Holtmann
2011-02-03 12:22 ` mikhail.zabaluev
2011-02-03 16:11 ` Denis Kenzior
2011-02-04 9:23 ` mikhail.zabaluev
2011-02-04 12:58 ` Marcel Holtmann
2011-02-04 16:52 ` mikhail.zabaluev
2011-02-04 17:05 ` Denis Kenzior
2011-02-04 18:07 ` mikhail.zabaluev
2011-02-04 18:13 ` Marcel Holtmann
2011-02-04 18:52 ` mikhail.zabaluev
2011-02-04 19:01 ` Denis Kenzior [this message]
2011-02-04 19:01 ` Marcel Holtmann
2011-02-04 19:33 ` mikhail.zabaluev
2011-02-04 19:48 ` Marcel Holtmann
2011-02-04 18:27 ` Denis Kenzior
2011-02-04 19:17 ` mikhail.zabaluev
2011-02-04 19:22 ` Marcel Holtmann
2011-02-04 19:27 ` Denis Kenzior
2011-02-04 17:15 ` Marcel Holtmann
2011-02-04 18:32 ` mikhail.zabaluev
2011-02-02 22:55 ` Kai.Vehmanen
2011-02-02 23:06 ` 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=4D4C4CFE.3010508@gmail.com \
--to=denkenz@gmail.com \
--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.