On 2006-01-23 11:11:25, Edi Weitz wrote:
OK, thanks for the info. I've been thinking about extracting the relevant bits from KMRCL and integrating them into TBNL directly anyway. We only use a small fraction of what's in there and it might make sense to make some of this user-configurable, not only because of the external format but also because of the interface(s) TBNL will listen on, for example. I'll do that one day... :)
Last time I checked only the following symbols are used:
kmrcl:listener kmrcl::with-lock-held kmrcl:close-active-socket kmrcl:init/listener kmrcl::make-lock
The locking stuff is easy. But for the sockets I'd try some other, specialized library. Less to maintain for TBNL.
Are there any portable libraries for the multiprocesing/threading stuff (Listener)?