Received: with ECARTIS (v1.0.0; list gopher); Mon, 15 Apr 2002 16:48:46 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from tomts24-srv.bellnexxia.net (tomts24.bellnexxia.net [209.226.175.187]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 43B973B811 for ; Mon, 15 Apr 2002 16:48:46 -0500 (EST) Received: from [209.226.175.22] by tomts24-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20020415214845.GABF6268.tomts24-srv.bellnexxia.net@[209.226.175.22]> for ; Mon, 15 Apr 2002 17:48:45 -0400 From: Ralph Furmaniak To: gopher@complete.org Subject: [gopher] Re: Views Date: Mon, 15 Apr 2002 17:48:45 EDT MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <20020415214845.GABF6268.tomts24-srv.bellnexxia.net@[209.226.175.22]> X-archive-position: 593 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: sugaku@sympatico.ca 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 > 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. Is there any point to this, or is it just so that it knows what to send to gopher0 clients? I had a file in text/plain and image/gif format. The server put image/gif as preferred. The umn client just picked text/plain as preferred.