> ""Leif Jackson"" <[EMAIL PROTECTED]> said: > >>> If we're using Glib, then let's also use Glib's threading interface. It >>> gives us transparency over a variety of thread implementations and >>> platforms, and provides for graceful failure in case there is no thread >>> implementation at all. >> >> The issue is that glib's thead pool won't work for an application server >> like dbmail, it is a pool or worker functions I wrote another program >> using glib's thread interface and it is a nightmare. I have a thread >> pool >> implementaion that is mostly from the pthreads book by o'reilly with >> real >> world updates and improments to it. It should be portable and if we make >> the threads configurable that would take care of the systems that don't >> allow for threads. > > > There are two sets of thread API's in Glib: Threads and ThreadPools. I > haven't used either, but Threads looks like an appropriate wrapper around > PThreads and Solaris threads. Does that address your thread pool concerns? >
No unfortunatly it doesn't exactly it makes the code a bit harder, I will work on tring to use the glib threads with my thread pool code and see what happens, it just adds an extra layer of code that isn't needed as threads are really not that hard to write well, primarly with the glib stuff it makes it 3 times as hard to debug and that is my main concern. -leif > > Aaron > > -- > _______________________________________________ > Dbmail-dev mailing list > Dbmail-dev@dbmail.org > http://twister.fastxs.net/mailman/listinfo/dbmail-dev >
