On Wed, May 31, 2017 at 04:02:42PM +0100, Daniel P. Berrange wrote: > On Wed, May 31, 2017 at 03:59:10PM +0100, Richard W.M. Jones wrote: > > On Thu, May 25, 2017 at 10:26:47AM -0700, Peter wrote: > > > The majority of cockpit is implemented in > > > javascript. > > > > How about using the gobject libvirt bindings? > > > > https://libvirt.org/git/?p=libvirt-glib.git;a=summary > > > > They should be usable from Javascript directly, as in the .js example > > here: > > > > https://libvirt.org/git/?p=libvirt-glib.git;a=tree;f=examples;h=d63d5964be2299b62140f9fd183b5cc744837d8a;hb=HEAD > > They're usable from a standalone javascript interpretor, but there's no > way to use them from a client side javascript interpretor in the user's > web browser. Hmm OK, I thought "implemented in javascript" meant they were using server-side Javascript. I see that cockpit runs two processes on the server (cockpit-ws and ssh-agent). I had a look at one of the modules in the source (pkg/systemd). It's running local commands (eg. "grep"), and issuing dbus calls which AFAIK cannot be issued over the network. Can Peter explain a bit more about the architecture of Cockpit? Where does the Javascript run? What JS engine runs it? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
