Bug 24376 - some way to deal with crashed observers
Summary: some way to deal with crashed observers
Status: RESOLVED DUPLICATE of bug 24768
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Senko Rasic
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-07 08:08 UTC by Simon McVittie
Modified: 2010-03-25 07:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Simon McVittie 2009-10-07 08:08:22 UTC
15:58 < wjt> it'd be useful if an observer could ask MC what channels it 
             *would* have been asked to observe, had it been running when they 
             were opened
15:59 < wjt> because otherwise when you're developing an observer and you 
             restart it, you need to restart all your channels before it 
             notices them
16:00 < sjoerd> being able to get all of the current channels might be good 
                enough for those use-cases though
16:01 < smcv> yeah, like the DispatchOperationList interface
16:01 < smcv> but MC already knows how to match channels against filters, so...
16:01 < sjoerd> yup
16:01 < smcv> it's inherently racy, of course - the observer working out what 
              it ought to be observing races with the handler ack'ing messages
16:02 < smcv> but it might be useful for observers that crash and auto-restart, 
              at least
16:02 < smcv> (in which case you already crashed, so potetially losing a few 
              messages is to be expected)
16:03 < wjt> hell, we could have an RestartMeIfICrash property
Comment 1 Simon McVittie 2010-03-16 06:01:05 UTC
This is closely related to Bug #24768, and might end up being the same implementation. Senko is working on it.
Comment 2 Simon McVittie 2010-03-25 07:21:36 UTC
The API proposed in Bug #24768 addresses this requirement too.

*** This bug has been marked as a duplicate of bug 24768 ***


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.