From owner-freebsd-chat Sat Nov 13 20:31: 9 1999 Delivered-To: freebsd-chat@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id ED22C14A27; Sat, 13 Nov 1999 20:31:00 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id UAA29198; Sat, 13 Nov 1999 20:56:28 -0800 (PST) Date: Sat, 13 Nov 1999 20:56:27 -0800 (PST) From: Alfred Perlstein To: Kris Kennaway Cc: Jonathon McKitrick , freebsd-chat@FreeBSD.ORG Subject: Re: threads.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 13 Nov 1999, Kris Kennaway wrote: > On Sat, 13 Nov 1999, Jonathon McKitrick wrote: > > > Here's a perfect example of when threads matter.. i want the newest > > version of Licq. The newest, with all recent fixes, is 0.71. But i > > have to DL 0.61 because after that they became THREADED! I hope we have > > threads (kernel) soon. > > We already have threads. How exactly does licq (an ICQ client) rely on > kernel-supported threads (only needed for some level of SMP scalability?) The problem is that we require pthread_cancel for Licq to work, I ported it over from OpenBSD a while back and handed it over to the thread guru Daniel E, he's cleaned up a few rough edges and plans on integrating it soon. why a chat client needs to be multithreaded especially using dangerous thread functions (pthread_cancel) is beyond me... but then again, everything is automagically faster/better with threads right? :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message