Browse files

Update the README

  • Loading branch information...
1 parent 99211e1 commit 01a10bf2454fcd98e389d193ce5ce1e5bac373ea @msantos committed Feb 28, 2011
Showing with 11 additions and 15 deletions.
  1. +11 −15
@@ -1,6 +1,16 @@
Erlang bindings to the libvirt virtualization API.
+An (almost) pure Erlang libvirt binding is available here:
+This version uses the libvirtd remote procotol over a Unix socket.
The libvirt API is not safe.
@@ -12,12 +22,6 @@ Erlang bindings to the libvirt virtualization API.
between the same functions for different resources and the sheer
size of the API mean that there will be mistakes.
- There isn't really a reason to call the libvirt API directly since
- libvirt provides a command line shell (virsh) that can be run as a
- port. The usual reasons given for using an NIF (speed, libraries)
- in this case don't really apply since virsh looks to be complete and
- using it as a port is much safer. Alternatively, it may be possible
- to talk to libvirtd directly from Erlang.
@@ -52,7 +56,7 @@ Erlang bindings to the libvirt virtualization API.
This example is the Erlang equivalent of a Python script to manipulate a
running domain. The example is taken from:
@@ -108,14 +112,6 @@
-* verp: a port version of the NIF Erlang libvirt bindings
- * look at creating a libvirtvirt (libvert) abstraction so the C code
- can be shared between the port and NIF
-* verx: (almost) pure Erlang libvirt binding
- * communicate directly with the libvirtd socket using the remote
- protocol
* tests: use the libvirt test driver and make a set of tests
* review the Erlang interface

0 comments on commit 01a10bf

Please sign in to comment.