>Fri Oct 03 2008 05:00:41 EDT from [EMAIL PROTECTED] >Subject: Re: Peak memory usage > > > >webcit has the concept of worker threads, much like apache. it increases >/ decreasess the pool on need. > >when a request comes in, the context_loop() parses it, and either goes to >logon and creates a new wcsessios struct and puts it to the static list. The >list is kept in global context, and is protected by a mutex. A thread >becommes sessioned by being put the wcsession pointer into its thread >specific data. the WC macro retrieves it. To reduce load on >getthreadspecificdata() you will sometimes see WCC=WC at the top of a >function; The session isn't passed on in any requests.
It seems like webcit can only serve one request per session at a time; and if I am downloading a large attachment, I cant read any other messages. Perhaps when the response is being sent, webcit could let go of the WC as it won't need it any more, and then another request can be served. Sam
