Re: Mysterious socket error

I did not mean thread_per_channel, I meant "thread per channel" - one
worker thread for each channel a session contains.  It's probably 10 - 20
lines of wrapper code change.

BTW, there is memory leak/socket leak/thread leak in the beepcore-c
library (or should I say pilot error).  An example: the worker threads
probably should call pthread_detach() as the first thing...

Lei

On Sat, 10 Jan 2004, David C Niemi wrote:

> On Fri, 9 Jan 2004, Lei Zhang wrote:
> > I've noticed this too.  I changed the threading model to one thread per
> > channel a couple of months ago, that probably explains why I'm not
> > having the problem that's bothering David.
>
> As far as I can see, this is NOT what thread_per_channel does -- without
> it, there would be only one thread allocated total, as opposed to one per
> channel.  Although pfa() does seem to get called multiple times
> concurrently, evidently meaning there are multiple threads.


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html