For example option compress controls kind of compression that client
performs when saving data to server. Similarly cache-size, logfile and
read-only adjust on-client behaviour, not server.
From https://lab.nexedi.com/nexedi/neoppod/merge_requests/18#note_124725 :
In general the most correct thing to do is:
- use host part for where to connect (host:port, list of host ports, UNIX socket, etc)
- use path part to identify a database or other on-server resource
- use query part for parameters that are passed to remote server (e.g. `storage` in case of ZEO)
- use fragment part for local parameters that are not passed to remote server (e.g. local `logfile`)
- use credentials part for things required to authenticate/encrypt.
To normalize an URL wcfs client would drop credentials and fragment, but keep host, path and query.
Fragments are documented not to be sent to remote side and to be evaluated by local side only.-> Move options that control client behaviour to fragment.