That's correct. But the recent posts show that gnugk
socket implementation outperforms the one from pwlib
in terms of cpu usage. Of course, the problem may be
not in pwlib but in the way gnugk is using sockets.
Another thing is that gnugk implementation is rather
a minimalistic one;)
I've also found a way to improve gnugk socket code
performance (for both pwlib and gnugk sockets),
so maybe the results will be much better.
----- Original Message -----
From: "Craig Southeren" <craigs@xxxxxxxxxxxxxxxxx>
Sent: Friday, April 16, 2004 5:34 PM
On Fri, 16 Apr 2004 12:12:47 +0200
"Zygmuntowicz Michal" <m.zygmuntowicz@xxxxxxx> wrote:
..deleted
>
> If you have gnugk compiled with large_fdset enabled, then pwlib sockets
> implementation is replaced with the lightweight one from gnugk.
PWLib incorporated large FD set support many months ago as a standard
feature, and will automatically use the maximum number of per-process
handles allowed by the host operating system as indicated by the rlimit
function.
Craig
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/
