Bug 254474 - [api] Need synchronous ISubSystem#disconnect() API and/or callback for async disconnect()
Summary: [api] Need synchronous ISubSystem#disconnect() API and/or callback for async ...
Status: NEW
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: David McKnight CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks: 251026
  Show dependency tree
 
Reported: 2008-11-06 12:01 EST by Martin Oberhuber CLA
Modified: 2009-03-18 15:35 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2008-11-06 12:01:35 EST 
In order to fix bug 251026, we'll need new API to synchronously disconnect a subsystem, such that the client knows if and when the disconnect finished successfully.

This can either be a synchronous disconnect(IProgressMonitor), or an asynchronous disconnect(boolean, ICallback) with a callback to inform about status. I'm slightly more in favor of the synchronous variant since it is more in line with what we're doing in the connector service.

Adding this API in a backward compatible non-breaking fashion should be easy.
Comment 1 David McKnight CLA 2009-03-18 15:35:31 EDT 
Would it not be an option to just ask that a client call subsystem.getConnectorService().disconnect(IProgressMonitor)?