SRV Request UI operations; UIs should implement this if they want to do SRV lookups themselves, rather than relying on the core. More...
#include <dnssrv.h>
Data Fields | |
gboolean(* | resolve )(PurpleSrvTxtQueryData *query_data, PurpleSrvTxtQueryResolvedCallback resolved_cb, PurpleSrvTxtQueryFailedCallback failed_cb) |
If implemented, return TRUE if the UI takes responsibility for SRV queries. | |
void(* | destroy )(PurpleSrvTxtQueryData *query_data) |
Called just before query_data is freed; this should cancel any further use of query_data the UI would make. | |
void(* | _purple_reserved1 )(void) |
void(* | _purple_reserved2 )(void) |
void(* | _purple_reserved3 )(void) |
void(* | _purple_reserved4 )(void) |
SRV Request UI operations; UIs should implement this if they want to do SRV lookups themselves, rather than relying on the core.
Definition at line 66 of file dnssrv.h.
void(* PurpleSrvTxtQueryUiOps::destroy)(PurpleSrvTxtQueryData *query_data) |
Called just before query_data is freed; this should cancel any further use of query_data the UI would make.
Unneeded if resolve_host is not implemented.
gboolean(* PurpleSrvTxtQueryUiOps::resolve)(PurpleSrvTxtQueryData *query_data, PurpleSrvTxtQueryResolvedCallback resolved_cb, PurpleSrvTxtQueryFailedCallback failed_cb) |
If implemented, return TRUE if the UI takes responsibility for SRV queries.
When returning FALSE, the standard implementation is used. These callbacks MUST be called asynchronously.