Re: Bug in log.c
Stipe Tolj <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Organization | Wapme Systems AG |
| Message-ID | <[email protected]> |
Nisan Bloch schrieb: > > Hi > > We run into this all the time with out SMPP server. Threads are spawned for > new ESME connections and terminated on disconnect. Some of our users > connect and disconnect very regularily and the thread-id often goes over > 1024. This however means quite a few changes to the way the log stuff > currently works. We may have to use a list instead of an array. hmmm, list are *slow* compared to a fixed array. You have to keep in mind that the logging functions are caller *really* a lot of times anywhere in the code, so the mapping has to be as fast as possible. Is there any concern in changing gwthread-pthread.c code in cycling between 1-1024 for the thread_ids instead of incrementing?! Stipe [email protected] ------------------------------------------------------------------- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [email protected] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are