On Fri, Feb 26, 2016 at 05:53:34PM +, Daniel P. Berrange wrote:
> On Wed, Feb 17, 2016 at 03:14:53PM +0300, Nikolay Shirokovskiy wrote:
> > Currently close callback API can only inform us of closing the connection
> > between remote driver and daemon. But what if a driver running in the
> > dae
On 26.02.2016 20:53, Daniel P. Berrange wrote:
> On Wed, Feb 17, 2016 at 03:14:53PM +0300, Nikolay Shirokovskiy wrote:
>> Currently close callback API can only inform us of closing the connection
>> between remote driver and daemon. But what if a driver running in the
>> daemon itself can have an
On Wed, Feb 17, 2016 at 03:14:53PM +0300, Nikolay Shirokovskiy wrote:
> Currently close callback API can only inform us of closing the connection
> between remote driver and daemon. But what if a driver running in the
> daemon itself can have another persistent connection? In this case
> we want to
Currently close callback API can only inform us of closing the connection
between remote driver and daemon. But what if a driver running in the
daemon itself can have another persistent connection? In this case
we want to be informed of that connection changes state too.
This patch series extends
