On Sep 8, 2006, at 5:27 PM, Chris Hostetter wrote:
: i'm +1 on this idea that the server should be configurable in ways
: the client cannot affect, if so desired, or configured such that the
: client has control over all the parameters - but let's make the
: controllability of parameters configurable itself. surely there are
You totally lost me there ... "controllability of parameters
configurable
itself" ... can you clarify what you mean by that?
Sorry, sounds awkward in re-reading what I wrote myself. I think you
and I are saying the same thing... allow parameters to have default
configuration server-side, allowing them to be overridden by request
parameters is how it currently works (right?) but perhaps some
parameters don't make sense in some uses for a client to control, so
locking them off to strictly the server-side setting should be
possible. I'm not sure where this use case would be either, but we
are approaching quite a lot of parameters a client would be sending
to get search, sort, start, limit, highlighting, faceting, and soon
"more like this", and so on. Maybe what we want is a way to have
named sets of parameter settings in the configuration file and allow
a request to use a pre-set by a simple name, keeping the HTTP request
slimmer.
You know, like pressing "1" on the radio to get WNRN 91.9 :) (except
with volume, treble, bass, etc settings built into that button also)
Erik
