Thanks everyone for their thoughts: I've considered the feedback, especially Gordon's point that the server mechanisms are already configured using the SASL configuration file which you need in any case to set up the authenticatino db.
I think the issue is still enough of a speed bump to new developers that I've decided to go ahead and make this a purely client side filter. In this case there won't be any confusion over proton opaquely changing the mech list from what the SASL config file lists. I've gone with with the simplest no extra API option - this can certainly change is it turns out to be a problem. The new PR is in the same place [1] and I'll merge this soon unless there are serious objections. Andrew [1] https://github.com/apache/qpid-proton/pull/148
