From: Ralph Furmaniak <sugaku@sympatico.ca>
To: gopher@complete.org
Subject: [gopher] Re: Views
Date: Mon, 15 Apr 2002 17:33:09 EDT
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Message-Id: 
 <20020415213309.MVKN4519.tomts13-srv.bellnexxia.net@[209.226.175.22]>
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


> In that case, the harder question to ask is: how can a client tell 
> the server what's preferred?

Why would it need to?  The server lists the views and the client requests whichever of these it wants.  This is the way the current protocol works, the client sends (where F means tab) selectorF+view where view is the view requested.

Putting the logic in the client might be the best, even though that's what was perhaps avoided in the past.

Only the person really knows the preferences, but the programs (clients,servers) can still themselves choose preferences.  For example it would rather take gif than bmp.  I do agree that the client knows best though, for example it is really depended on the client OS whether they would take tgz, zip, or the mac format.