Received: with ECARTIS (v1.0.0; list gopher); Mon, 15 Apr 2002 16:42:33 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from christoph.complete.org (unknown [168.215.193.254]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 517D53B811 for ; Mon, 15 Apr 2002 16:42:33 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by christoph.complete.org (Postfix) with ESMTP id 443E15A344 for ; Mon, 15 Apr 2002 16:42:32 -0500 (EST) Date: Mon, 15 Apr 2002 16:42:31 -0500 Subject: [gopher] Re: Views Content-type: text/plain; charset=US-ASCII Mime-Version: 1.0 (Apple Message framework v481) From: John Goerzen To: gopher@complete.org Content-Transfer-Encoding: 8bit In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.481) X-archive-position: 592 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-ID: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher On Monday, April 15, 2002, at 04:04 PM, Robert Hahn wrote: > If you're open to changing the spec, then perhaps it should be up to > the client to specify what's 'preferred'. How can the server know > what a client wants, really? It doesn't have to. The client just gets what it wants. The server simply tells it what the option is and indicates a single preferred option (the first listed one). The client can either heed or ignore that preference.