On Thu, Jul 05, 2007 at 02:06:08PM +0530, Shuveb Hussain wrote: > Hi Daniel, > > > Oh at the C level, definitely ! The python layer is really only a > > language > >binding wrapper and should remain that way ! Even if we fork as a new > >process > >the python side of libvirt is packaged separately, and really the core > >should > >be written in C, this would also allow to merge back your code in the > >existing > >daemon code if needed. > > I understand the Python bindings part. I was wondering if the daemon > itself could be written in Python, since I have to deal with a lot of > text parsing from the OpenVZ utils. The LibVirt part that will talk to > the daemon over the proxy/pipe code will anyways have to be C. I would really prefer C so we can merge daemon code if needed. I know a bit about textual parsing, I'm not afraid by this, in my experience doing proper pipe protocol is way harder and we have that working which you can reuse nearly as is. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard@xxxxxxxxxx | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list