On 04/28/2016 04:04 AM, Michal Privoznik wrote:
Even though there's no way how to make stream seekable right now,
s/how //
it is going to be soon. We need to track this info so that we don't send virStreamSkip to a client that did not want it or vice versa.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> ---
+++ b/daemon/stream.c @@ -52,6 +52,8 @@ struct daemonClientStream { virNetMessagePtr rx; bool tx;
+ bool seekable;
This is not random-access, but just fast-forward, correct? Maybe 'skippable' (or would that be 'skipable'?) is a better term than 'seekable', since we are only skipping forwards rather than seeking to arbitrary offsets, and since the API was named virStreamSkip rather than virStreamSeek. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org