From owner-freebsd-chat Mon Jan 12 12:22:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA24471 for chat-outgoing; Mon, 12 Jan 1998 12:22:56 -0800 (PST) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from xmission.xmission.com (softweyr@xmission.xmission.com [198.60.22.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA24343; Mon, 12 Jan 1998 12:21:10 -0800 (PST) (envelope-from softweyr@xmission.xmission.com) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.7/8.7.5) id NAA03478; Mon, 12 Jan 1998 13:20:58 -0700 (MST) From: Wes Peters - Softweyr LLC Message-Id: <199801122020.NAA03478@xmission.xmission.com> Subject: Re: Book Request To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Mon, 12 Jan 1998 13:20:56 -0700 (MST) Cc: chat@FreeBSD.ORG In-Reply-To: <199801120042.QAA25634@hub.freebsd.org> from "Jonathan M. Bresler" at Jan 11, 98 04:42:03 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wes Peters lamented: % I wish W. Richard Stevens would come back from the lecture circuit long % enought to put together a really good TCP/IP illustrated volume 4, and % cover HTTP, TLS, and many of the relatively new internet protocols; I % could have really used such a book this last year. Jonathan M. Bresler replied: > HTTP is covered in volume 3. But only just barely; he basically looks at the socket usage from HTTP/1.0 client/server connections. What I really wanted was a good discussion of how the HTTP/1.1 protocol is suppose to work. Which headers do you use to reliably specify that you're using keep-alive connections, and how long the connections will stay alive? What does your sever need to do to achieve high throughput? Etc. HTTP is really quite a complex protocol at the 1.1 level; I fear what the "design committee" has done to the 2.0 protocol. > what's TLS? Transport Layer Security -- the draft IETF standard based on SSL. It is alarmingly difficult to find any documentation on how to implement the protocol for https:// URLs. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com