-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generic settings api #232
base: master
Are you sure you want to change the base?
Generic settings api #232
Conversation
320edcf
to
7dbdc2a
Compare
@pasis what do you think of this idea? |
7dbdc2a
to
32f4871
Compare
I like the direction. But JID (and probably password) sounds to me like something more important than just a setting. Not critical, just my preferences. |
Cool! Nice to hear.
I also thought about whether there's some more important things that deserve a separate API and the JID/password was on that list. I ended up putting everything in there, since if you use SASL-EXTERNAL via client certificates to authenticate, there's no JID (or password) required. You could give a JID, if you want to authenticate as a different user than given in the certificate, but that's just an option. |
8f4a9cd
to
0ce84f8
Compare
0d573b4
to
3f03de0
Compare
0ce84f8
to
01928af
Compare
@singpolyma do you have an opinion on this PR? |
feels more or less the same to me. a matter of taste |
Instead of having a multitude of setter API functions for configuration options, provide generic ones for the different types we have. Signed-off-by: Steffen Jaeckel <[email protected]>
Signed-off-by: Steffen Jaeckel <[email protected]>
01928af
to
541c22c
Compare
Introduce generic
xmpp_conn_set_*()
APIInstead of having a multitude of setter API functions for configuration options, provide generic ones for the different types we have.