On 09/13/2010 02:21 AM, 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... > > Thanks, > Chase > _____
Chase, I'd target confdb, cpg, and quorum. sam is a C only API - not sure how well scripting languages would work with that. As for SWIG/not swig, having any bindings at all is an improvement. Thanks again for the efforts. Regards -steve __________________________________________ > 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
