Top | ![]() |
![]() |
![]() |
![]() |
GQuark | inf_request_error_quark () |
const gchar * | inf_request_strerror () |
GQuark | inf_user_error_quark () |
const gchar * | inf_user_strerror () |
GQuark | inf_directory_error_quark () |
const gchar * | inf_directory_strerror () |
GQuark | inf_authentication_detail_error_quark () |
const gchar * | inf_authentication_detail_strerror () |
GQuark | inf_gnutls_error_quark () |
void | inf_gnutls_set_error () |
GQuark | inf_gnutls_certificate_verification_error_quark () |
void | inf_gnutls_certificate_verification_set_error () |
GQuark | inf_gsasl_error_quark () |
void | inf_gsasl_set_error () |
enum | InfRequestError |
enum | InfUserError |
enum | InfDirectoryError |
enum | InfAuthenticationDetailError |
This section defines some common error codes that are used on both client and server side in infinote, and maps these to GErrors.
GQuark
inf_request_error_quark (void
);
Error domain for request errors. Errors in this domain will be from the InfRequestError enumeration. See GError for information on error domains.
const gchar *
inf_request_strerror (InfRequestError code
);
Returns a human-readable string for the given error code.
GQuark
inf_user_error_quark (void
);
Error domain for user-related errors. Errors in this domain will be from the InfUserError enumeration. See GError for information on error domains.
const gchar *
inf_user_strerror (InfUserError code
);
Returns a human-readable string for the given error code.
GQuark
inf_directory_error_quark (void
);
Error domain for directory errors. Errors in this domain will be from the InfDirectoryError enumeration. See GError for information on error domains.
const gchar *
inf_directory_strerror (InfDirectoryError code
);
Returns a human-readable string for the given error code.
GQuark
inf_authentication_detail_error_quark (void
);
Error domain for further information on authentication errors. Errors in this domain will be from the InfAuthenticationDetailError enumeration. See GError for information on error domains.
const gchar *
inf_authentication_detail_strerror (InfAuthenticationDetailError code
);
Returns a human-readable string for the given error code.
GQuark
inf_gnutls_error_quark (void
);
Error domain for GnuTLS errors. Errors in this domain will be GnuTLS error codes. See GError for information on error domains.
void inf_gnutls_set_error (GError **error
,int error_code
);
Sets a GError from a GnuTLS error code. If error
is NULL
, does nothing.
GQuark
inf_gnutls_certificate_verification_error_quark
(void
);
Error domain for GnuTLS certificate verification errors. Errors in this
domain will be GnuTLS certificate verification results as returned by
gnutls_certificate_verify_peers2()
. See GError for information on
error domains.
void inf_gnutls_certificate_verification_set_error (GError **error
,int verify
);
Sets a GError from a certificate verification result.
If error
is NULL
, does nothing.
GQuark
inf_gsasl_error_quark (void
);
Error domain for GNU SASL errors. Errors in this domain will be GNU SASL error codes. See GError for information on error domains.
These are general request errors that all InfcRequests can fail with. Specific requests may also fail with more errors, such as InfDirectoryError.
The server sent <request-failed/> with an unknown error domain. |
||
An error occurred while processing the server reply for a request. |
||
The server sent an invalid sequence number in a reply to a request. |
||
A request did not contain a XML attribute that is required to complete the request. |
||
A request contains an XML attribute with unexpected content. |
||
A number in a request was invalid. Either it was not numerical, or it produced an underflow or an overflow. |
||
The requesting host is not authorized to perform the requested action. |
||
Generic error code when no further reason of failure is known. |
These are errors related to users. They may occur during user join or during processing a user-related message, such as a user status change message in an InfSession.
The requested name is already in use by another user. |
||
The client provided a user ID field in a user join request, but it's the server's job to find an ID. |
||
A request referred to a user ID that no user is associated with. |
||
The initial user status was given as unavailable during user join or rejoin. |
||
The user did not join from the connection the request comes from. For example, a user status change can only be requested from the same connection that joined the user. |
||
An invalid status was used in a XML request. Allowed status values are "unavailable", "inactive" or "active". |
||
Generic error code when no further reason of failure is known. |
These are errors related to the directory of documents. These errors can be reason why requests created by InfcBrowser fail.
A client did not receive the directory's initial welcome message. |
||
The server and client use different versions of the protocol. |
||
A node with the given name exists already in that subdirectory (in response to node creation requests). |
||
A node with an invalid name was attempted to be created. |
||
The node refered to in a request does not exist in the directory (anymore). |
||
A <subscribe-ack> or <subscribe-nack> has been received without a previous request. |
||
A client attempted to subscribe to a server's chat, but the chat is disabled on the server side. |
||
The node refered to in a request is not a subdirectory node, but the requested operation requires one. |
||
The node refered to in a request is not a note (non-subdirectory) node, but the requested operations requires one. |
||
The node type is not supported by the server. |
||
A <remove-node> request attempted to remove a directory's root node, which is not allowed. |
||
An operation cannot be performed because the corresponding node is not explored. |
||
The node given in an exploration request has already been explored earlier. |
||
Exploration has begun before the client was told how many entries to expect. |
||
Exploration yields more children than announced at the beginning of the exploration. |
||
Exploration yields less children than announced at the beginning of the exploration. |
||
The type of a note is not known. |
||
The connection already subscribed to the node refered to, but the requested operation requires it to be unsubscribed. |
||
The connection is not subscribed to the node refered to, but the requested operation requires it to be subscribed. |
||
The server does not support the network of the incoming connection for the requested operation. For example, subscribing to a session might require a network that has a peer-to-peer communication method, but there is no implementation of that method for the connection's network. |
||
The server requested a communaction method for subscription or synchronization that is not supported by the client. |
||
The requested operation is not supported by the server. |
||
A client received a <sync-in/> without having requested one. The client has no data to sync to the server. |
||
A client replied with <subscribe-nack> on an attempt to subscribe it to a session. |
||
A message that is not understood was received. |
||
A node cannot be stored permanently on the server since it has no storage backend attached. |
||
An invalid certificate or certificate request have been sent. |
||
The account list has already been queried before. |
||
The account list has not been queried. |
||
When adding a new account the new account ID exists already in the account list. |
||
There is no such account with the given ID. |
||
The ACL for a node has already been queried before. |
||
The ACL for a node has not yet been queried, but is required to perform the operation. |
||
Generic error code when no further reason of failure is known. |
These errors can give an additional hint why the SASL authentication failed.