On Tue, 2010-03-16 at 00:14 -0700, Steven Dake wrote: > On Tue, 2010-03-16 at 17:47 +1100, Angus Salkeld wrote: > > Hi > > > > I found this a handy library whilst writing the cpg_test_agent > > for the test harness. Others might find it useful too. > > We currently have quite a few exposed (generic) libraries > > perhaps this could be one of them (logsys, ipc/s, etc ...). > > > > coropoll is exported currently via a header file, although I am not sure > it is packaged as a DSO. I had hoped people would start to use the > non-cluster APIs available in Corosync for their own client/server > applications, but as a developer when I think Corosync I think "cluster > software". This thought pattern may be a general condition of the other > client/server-ish apis in Corosync. It may be that providing those > reusable components is outside the mission and general audience of the > Corosync community. > It might be more useful to remove these more general parts into a separate library like many other projects have done. It will help to harden the library and focus corosync on it's prime mission (clustering).
-Angus > Regards > -steve > > > Regards > > Angus > > > > > > _______________________________________________ > > 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
