On Tuesday 18 October 2005 10:37 am, Geo Carncross wrote: > I should clarify, that providing a common API to the language bindings > isn't bad, but requiring that they use them is- that is, having other > parts of OW use the same mutexes and locks and whathaveyou that the OW > language bindings do.
You're right. In general they do share all the same synchronization/locks. That's what made allowing simultaneous reads and writes so easy. The only problem is that owfs, owhttpd and owserver can strictly enforce the order that owlib setup, use, and shutdown occur. Allowing those primatives in the language bindings requires a check. I've now put that check in owlib, with simple calls to bracket use in the language bindings. This follows our general philosophy of making owlib heavy and all the other programs light. Paul ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers