From owner-freebsd-isp Thu Jan 15 18:42:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13692 for freebsd-isp-outgoing; Thu, 15 Jan 1998 18:42:16 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13683 for ; Thu, 15 Jan 1998 18:42:10 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-80.HiWAAY.net [208.147.148.80]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id UAA14309; Thu, 15 Jan 1998 20:42:11 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id UAA11703; Thu, 15 Jan 1998 20:10:20 -0600 (CST) Message-Id: <199801160210.UAA11703@nospam.hiwaay.net> X-Mailer: exmh version 2.0.1 12/23/97 To: Joe Mays cc: freebsd-isp@FreeBSD.ORG From: David Kelly Subject: Re: Distributed Webservers In-reply-to: Message from Joe Mays of "Wed, 14 Jan 1998 16:40:11 EST." <34BD30BB.CD46E7FA@launchpad.win.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Jan 1998 20:10:20 -0600 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > What are the favored methods for running distributed > load-balancing webservers here? That prompts a question I've been thinking about how to ask. Maybe I'll find the words to ask it properly. In the nature of WWW, with hyperlinks all over the place, we have a customer who wants authenticated logins to all of their sites, scattered hither and yon. On following a hyperlink to another site (part of their system) is not happy with an additional password challenge. Others are working this problem, but from what I hear the supposed solution involves purchasing everything in Netscape's catalog. Any suggestions? Sample code? -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.