Currently the default is to load every scope for a client, then remove what is explicitly denied. This was done originally to make deploying the client (intended as a very simple sample) a snap. Evolution has made the client central to any number of operations such as proxying and this is now counter-intuitive and annoying.
The expected behavior is that only listing a scope explicitly adds it to the client's request list. Optionally it may be disabled (mostly so you don't have to go to the trouble of removing it from the configuration for, say, debugging purposes).
Currently the default is to load every scope for a client, then remove what is explicitly denied. This was done originally to make deploying the client (intended as a very simple sample) a snap. Evolution has made the client central to any number of operations such as proxying and this is now counter-intuitive and annoying.
The expected behavior is that only listing a scope explicitly adds it to the client's request list. Optionally it may be disabled (mostly so you don't have to go to the trouble of removing it from the configuration for, say, debugging purposes).