On Mon, Sep 13, 2010 at 2:36 PM, Florian Haas <[email protected]> wrote: > On 2010-09-13 11:21, Chase Venters wrote: >> On Monday 13 September 2010 3:45:50 am Florian Haas wrote: >>> I realize I may be asking for a lot, but is there any chance you could >>> rewrite your module to use SWIG, thereby making it more easily portable >>> to languages other than Perl? >> >> I definitely see the value of having pieces of the corosync stack exposed to >> more scripting languages. >> >> I've only glanced briefly at SWIG before. That was a few years ago. To be >> honest I don't remember why I've tended to pass up SWIG for XS, but I'm happy >> to take another look at it SWIG when I find some time. Thankfully the CPG API >> is nice and simple which made these bindings easy to create. >> >> Along these same lines, I wonder what other parts of the stack would be most >> useful to expose? I've been thinking about doing something with the confdb... > > Are you using Pacemaker at all? If so, an object oriented wrapper around > libcib would be high on my personal list. Probably best done as a C++ > wrapper around the libcib C API,
/me cries > and then SWIG interfaces to expose the > CIB to OO languages like Python and Ruby. > > Cheers, > Florian > > > _______________________________________________ > Openais mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/openais > _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
