Hi Sarah, What are the intended languages and language interactions for the new modules and users of those modules? For example, beadm is written in Python and uses libbe_pymod to bridge the gap from Python to C, to communicate with libbe. Is the intent that the standard modules support this kind of bridging, or would an additional layer sit between module and python program, or would a python program require a new module for each library it intends to use?
library <-> standard module <-> python program library <-> standard module <-> pymod <-> python program library <-> consumer module <-> python program Sarah Jelinek wrote: > Hi All, > > I have posted the first public draft of the proposed Caiman Unified > Engine Functional specification. It is located > at: > > http://opensolaris.org/os/project/caiman/CUD/CUE_docs/CUD_func_spec.pdf > > General Caiman Unified Engine project page is here: > > http://opensolaris.org/os/project/caiman/CUD/ > > With more documentation linked off this page for reference. The intent > of this project is to provide a unified engine and a streamlined > architecture and model for Caiman Engine consumers. > > We are asking for review and comments on our proposal. Your comments > are important to us. > > Thank you for your time. > > Regards, > sarah > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
