Re: [libvirt] [PATCH v3 28/31] gendispatch: Introduce @sparseflag for our calls

2017-05-17 Thread Michal Privoznik
On 05/17/2017 05:32 PM, John Ferlan wrote: > > > On 05/16/2017 10:04 AM, Michal Privoznik wrote: >> Now, not all APIs are going to support sparse streams. To some it >> makes no sense at all, e.g. virDomainOpenConsole() or >> virDomainOpenChannel(). To others, we will need a special flag to >> in

Re: [libvirt] [PATCH v3 28/31] gendispatch: Introduce @sparseflag for our calls

2017-05-17 Thread John Ferlan
On 05/16/2017 10:04 AM, Michal Privoznik wrote: > Now, not all APIs are going to support sparse streams. To some it > makes no sense at all, e.g. virDomainOpenConsole() or > virDomainOpenChannel(). To others, we will need a special flag to > indicate that client wants to enable sparse streams. In

[libvirt] [PATCH v3 28/31] gendispatch: Introduce @sparseflag for our calls

2017-05-16 Thread Michal Privoznik
Now, not all APIs are going to support sparse streams. To some it makes no sense at all, e.g. virDomainOpenConsole() or virDomainOpenChannel(). To others, we will need a special flag to indicate that client wants to enable sparse streams. Instead of having to write RPC dispatchers by hand we can ju