Didnt know if this should to go "everything unix" or here so il give it a shot here first :> Read a "how-to" on using the unix/linux kernel sigs to do realtime comunication with sockets, and not getting a large list of idle sockets to use, basicly it just sends a sig to you when a socket is ready to use, but then .. something bad has to come out of this also right? Then there was something about using the kernels queue system, seem quite nice, thread safe and just "open("name");" almost to open the queue in another thread and start reading from it. These 2 could be combined to a pritty powerfull machine if used correctly i have a feeling, no waste in time to check all the sockets, no select() no poll() and THAT should drag down the cpu usage one hell of a huge amount just "waitsig(&sig);" :> ohh well, maybe someone is familiar with this? *hopes* and can tell me some pros and cons of this? if it could be used for large servers? Only problem i can see is if you try to make 2 "servers" and both try to create the same queue name ... as the queue i think, becomes system wide .. atleast application wide, that i know :> Ohh well, i hope for a respond from someone, gnite to you all and sleep well :>