Re: [libvirt] [Qemu-devel] Re: Supporting hypervisor specific APIs in libvirt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Anthony Liguori <anthony@xxxxxxxxxxxxx> writes:

> On 03/25/2010 07:37 AM, Avi Kivity wrote:
>> On 03/25/2010 02:33 PM, Anthony Liguori wrote:
>>>> From my point of view, i wouldn't want to write a high level
>>>> management toolstack in C, specially
>>>> since the API is well defined JSON which is easily available in
>>>> all high level language out there.
>>>
>>>
>>> There's a whole world of C based management toolstacks (CIM).
>>>
>>
>> Gratefully I know very little about CIM, but isn't it language
>> independent?
>>
>> The prominent open source implementation, pegasus, is written in C++.
>
> There is also SFCB which is written in C.
>
> But an awful lot of the providers for pegasus are written in C.
>
> The point is, C is a lowest common denominator and it's important to
> support in a proper way.

No.  The lowest truly common denominator is plain text.  And we got that
covered already.

A developer encountered the problem of talking a simple text protocol.
He thought "I know, I'll create a 1:1 C API for that".  Now he got two
problems.

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]