On 02/19/2014 04:06 AM, Daniel P. Berrange wrote:
> FWIW, for the initial 'virConnectOpen' API I think it probably would
> be worthwhile us supporting a standardized "timeout" URI parameter.
> That way if the remote service doesn't respond at all for some
> reason users can have fine control. That's a sufficiently targetted
> use case that it'd be easy to do, compared to timeouts for arbitrary
> APIs.
Indeed - having a timeout on the initial connection attempt is much more
useful than worrying about individual APIs when you have a responsive
connection, since it is the indeterminate time of establishing a remote
connection that may be the problem here. But does that mean yet another
C API? We already have virConnectOpen{,ReadOnly,Auth}. Or are you
envisioning this just in the language bindings (Java, python - but not C)?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list