core: add dynamic password infrastructure #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some media sources (e.g., DAAP) support notifying a client that
a password is required at connection time. Since such sources
are commonly detected with protocols like DNS-SD, Grilo needs a
mechanism to support handling such password requests.
This work adds a new "grl_source_notify_authenticate" function which a
plugin can call when a password is needed. The function, in turn, emits an
"authenticate" signal which the application should respond to by obtaining
a password. The application then provides the password back to the plugin
by calling the new "grl_daap_source_continue_with_password" function.
Signed-off-by: W. Michael Petullo [email protected]