From owner-freebsd-hackers Mon May 10 12:11:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 5201E15A73 for ; Mon, 10 May 1999 12:11:32 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id PAA29733; Mon, 10 May 1999 15:00:39 -0400 Date: Mon, 10 May 1999 15:00:39 -0400 (EDT) From: Zhihui Zhang To: "Justin C. Walker" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Sockets and SYSTEM V message queue In-Reply-To: <199905101838.LAA00711@rhapture.apple.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If your app is always going to run on a single system, there are > better ways to implement it. Local-domain sockets is one; pipes is > another (which may or may not be implemented with local-domain > sockets). SysV message queues could be used as well. Don't know > enough about their limitations to know whether it's a good choice, > though. > Thanks for the reply. I read some source code. In it, a server process create a single socket to accept packets from both local client processes and remote clients processes. This should be bad for performance. Am I right? According to your suggestion, it may be better to create one local-domain socket (I will figure how to use it later) for local clients and another socket for the remote clients. Regards, -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message