From owner-freebsd-net Mon Jun 11 20:27:53 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.jbu.com.cn (mail.jbu.com.cn [162.105.202.21]) by hub.freebsd.org (Postfix) with ESMTP id 04FC637B401 for ; Mon, 11 Jun 2001 20:27:51 -0700 (PDT) (envelope-from xiaohudong@263.net) Received: from hxd (watchdog.jbu.com.cn [162.105.202.150]) by mail.jbu.com.cn (8.9.3/8.9.3) with SMTP id LAA05738 for ; Tue, 12 Jun 2001 11:27:44 +0800 Message-Id: <200106120327.LAA05738@mail.jbu.com.cn> Date: Tue, 12 Jun 2001 11:30:43 +0800 From: xiaohudong To: "freebsd-net@freebsd.org" Subject: A question about Winsock style API X-mailer: FoxMail 3.1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello,I want to known if the development team has a plan to add Winnsock style API, such as WSAConnect and WSAAccept.I want to get the connection data to judge my program's behavior,I think these two APIs are very useful. I read the man page of accept,it says: For certain protocols which require an explicit confirmation, such as ISO or DATAKIT, accept() can be thought of as merely dequeueing the next con- nection request and not implying confirmation. Confirmation can be im- plied by a normal read or write on the new file descriptor, and rejection can be implied by closing the new socket. One can obtain user connection request data without confirming the con- nection by issuing a recvmsg(2) call with an msg_iovlen of 0 and a non- zero msg_controllen, or by issuing a getsockopt(2) request. Similarly, one can provide user connection rejection information by issuing a sendmsg(2) call with providing only the control information, or by call- ing setsockopt(2). So does anyone know something more? Thanks. xiaohudong xiaohudong@263.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message