From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: RE: [RFC 2/2] doc: Add description for history agent interface
Date: Fri, 04 Feb 2011 11:48:54 -0800 [thread overview]
Message-ID: <1296848934.1520.400.camel@aeonflux> (raw)
In-Reply-To: <A459777776EB4841B844E1134E7928740157CA57@008-AM1MPN1-016.mgdnok.nokia.com>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
Hi Mikhail,
> > > And the failure mode of the agent disconnecting is... to drop events
> > on the floor???
> >
> > Who said that? D-Bus is an asynchronous message bus with a method call
> > and a method return message. Where do you see events being dropped?
>
> When you receive a callback on NameOwnerChanged for the agent, the proposed patch, AFAICS, just nullifies the agent data in the history structure. Any history event handler called after that simply returns silently because the agent is not available.
> This is a lousy failure mode, and you'll need to improve it. Presumably, by spooling whole messages until there is an agent ready to receive them.
you do understand the concept of sending something as RFC, do you?
And I did clearly mentioned that the whole part of spooling call history
and message history when agent is not present is missing. That is a TODO
item and hence this was a RFC.
Regards
Marcel
next prev parent reply other threads:[~2011-02-04 19:48 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
2011-02-04 19:01 ` Marcel Holtmann
2011-02-04 19:33 ` mikhail.zabaluev
2011-02-04 19:48 ` Marcel Holtmann [this message]
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=1296848934.1520.400.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