Bug 22814 - 8.1.2. Receiving Messages should talk about channel dispatcher too
Summary: 8.1.2. Receiving Messages should talk about channel dispatcher too
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-doc (show other bugs)
Version: unspecified
Hardware: All All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL: http://people.collabora.co.uk/~davyd/...
Whiteboard:
Keywords:
Depends on: 24497
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-17 03:25 UTC by Tollef Fog Heen
Modified: 2019-12-03 19:15 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Tollef Fog Heen 2009-07-17 03:25:37 UTC
12:02 < Mithrandir> davyd: the suggestion in 
                    http://people.collabora.co.uk/~davyd/telepathy-book/sect.messaging.rich.html on 
                    not acking messages until they've been parsed so you get it again when the 
                    client reloads is a bit of a double edged sword, since you can then get into a 
                    crash scenario you can't get out of
12:03 < wjt> Mithrandir: the channel dispatcher solves that
12:03 < davyd> Mithrandir: yes, except Channel Dispatcher
12:03 < wjt> Mithrandir: it's responsible for blowing away a channel if its handler repeatedly dies
12:03 < Mithrandir> ah
12:03 < davyd> we probably should mention that
12:03 < Mithrandir> that sounds useful, maybe a comment about that should be added, yes.
12:05 < davyd> mmm
12:05 < davyd> I'm totally going to forget that
12:05 < davyd> file a bug against me
Comment 1 GitLab Migration User 2019-12-03 19:15:43 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-doc/issues/1.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.