> At the moment each such spawned thread has an entirely new I/O > system including its own private worker fifo: the garbage > collector and lexical context is shared, however. > I am looking for Felix bindings to mechanisms for the selection of procedures with less weight. Example: A "worker fifo" (current job queue approach) might not be completely needed to execute a single thread/task.
>> Do you find my suggestion "class for function calls that are not thread >> safe" useful? >> http://groups.google.de/groups?threadm=OtKbb.127587%24mp.64498%40rwcrnsc51.ops.asp.att.net >> http://groups.google.de/groups?threadm=34fu29F49rvasU1%40individual.net >> http://groups.google.de/group/comp.programming.threads/browse_frm/thread/68c6f7f993578408 >> > Not sure. Typically, it isn't just one function that is not re-entrant, > there is a protocol requiring multiple calls which need to be made > exclusively. > I imagine bindings to thread-unsafe C/C++ libraries. The calls/communication to their interfaces can be performed by dedicated threads that provide just the required mutual exclusion as a service. > Note Felix has a monitor object already .. it is in fact the > implementation of a Felix pre-emptive channel :) > http://felix.sourceforge.net/doc/rtl/doxygen/html/classflx_1_1pthread_1_1monitor__t.html I guess that I prefer a variant that will provide just a member function like "void execute(task& t, result& r)" instead of "void enqueue(void*)". Regards, Markus ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Felix-language mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/felix-language
