On 22/03/2016 11:25, Markus Armbruster wrote: > Regardless of how and when we create BlockBackend, we'll want to keep > the clean separation between frontend and backend internally and at the > user interface.
This means that the BlockBackend should not own the DriveInfo. The backend and frontend need not know of the object that mixes concepts from both of them. Instead, the DriveInfo can instantiate itself into a BlockBackend and the board can (if required) use the frontend parts of DriveInfo to instantiate a device and connect it to the BlocKBackend. In Kevin's idea there would be no ownership either way. Until then, I think my patch actually gets us closer to the ideal. Paolo > DriveInfo has no role in cleanly separate creation of frontend and > backend now, and it shouldn't get one in the future. Its purpose is to > support the legacy user interface that has frontend and backend matters > mixed up.