From: rajyalakshmi bommaraju <rajyalakshmi.bommaraju@intel.com>
To: ofono@ofono.org
Subject: Re: Please comment on callhistory API
Date: Mon, 27 Sep 2010 16:30:34 -0700 [thread overview]
Message-ID: <4CA1291A.3040909@intel.com> (raw)
In-Reply-To: <1285626082.9845.16.camel@aeonflux>
[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]
Hello Marcel,
Marcel Holtmann wrote:
> Hi Raji,
>
> this is the second time I have to remind you to not top post. Next time
> I will ignore your email. Just a friendly reminder to follow proper
> mailing list etiquette.
>
>
>> org.ofono.History will be the main adapter interface and
>> org.ofono.CallHistoryAgent the callhistory agent and
>> org.ofono.SmsHistoryAgent as the sms history agent. I want to seperate
>> the two agents so that sms app will expose sms history agent and dialer
>> will register and expose callhistory agent. Then it will be clear which
>> agent is interested in which history, vs one org.ofono.HistoryAgent
>> exposing ReportCall and ReportTextMessage methods. In the later case
>> adapter needs to flush both smshistory and callsistory onto two agents
>> even though agents are not interested only in type of history.
>>
>
> actually not really. So why does the dialer and SMS application need to
> register for the history? Isn't that going to be stored central in
> Tracker or something similar. Should not be Tracker or some Tracker
> helper be registering the agent?
>
No, Dialer and Sms applications are the ones that read and stores
locally, this will probably move to tracker eventually.
So I dont think we can assume that there is going to be a tracker agent.
> I might be wrong, but does it really make sense to separate it on this
> level?
>
I am thinking by separating the applications will only register and get
data they are interested in.
> And it needs to be MessageHistoryAgent if we decide to go for this. We
> banned the shortcut "sms" from the rest of the API.
>
> Regards
>
> Marcel
>
>
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> http://lists.ofono.org/listinfo/ofono
>
next prev parent reply other threads:[~2010-09-27 23:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 20:28 Please comment on callhistory API rajyalakshmi bommaraju
2010-09-24 1:17 ` Marcel Holtmann
2010-09-24 22:00 ` rajyalakshmi bommaraju
2010-09-27 17:50 ` Marcel Holtmann
2010-09-27 20:38 ` rajyalakshmi bommaraju
2010-09-27 22:21 ` Marcel Holtmann
2010-09-27 23:30 ` rajyalakshmi bommaraju [this message]
2010-09-28 14:08 ` Marcel Holtmann
2010-09-30 18:41 ` rajyalakshmi bommaraju
2010-10-01 7:33 ` Marcel Holtmann
2010-10-20 23:38 ` rajyalakshmi bommaraju
2010-09-27 23:08 ` Denis Kenzior
2010-09-27 23:14 ` Marcel Holtmann
2010-09-27 23:18 ` Denis Kenzior
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=4CA1291A.3040909@intel.com \
--to=rajyalakshmi.bommaraju@intel.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.