IrDA Framework

The following table lists variables in this documentation.

A connection is active.  
The base error code for all connection errors.  
The connection has been closed.  
A connection is not active.  
The connection has been terminated by unknown reason.  
The connection has been terminated by user.  
Unable to create connection complete event object.  
Unable to create a communication thread initialization event.  
A server was not able to create or init client connection instance.  
Unable to create communication termination event object.  
A server was not able to find a specific client connection class.  
Unable to create communication thread.  
Unexpected error.  
The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.  
The server was acting as a gateway or proxy and received an invalid response from the upstream server.  
The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).  
The base error code for OBEX errors.  
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates.  
An OBEX client is already connected to an OBEX server.  
The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent).  
Unable to create synchronization Mutex used to generate connection ID.  
The request has been fulfilled, resulting in the creation of a new resource.  
Indicates that the client requests that something be placed into a database but the database is full (cannot take more data).  
Returned when the client wishes to access a database, database table, or database record that has been locked.  
The error code indicates that the OBEX session has been disconnected by a remote side.  
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.  
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.  
Indicates that the resource requested is no longer available and will not be available again.  
The server does not support the HTTP protocol version used in the request.[  
A generic error, given when an unexpected condition was encountered and no more specific message is suitable.  
The operation can not be executed at this time. This error appears if for example an application calls Terminate for Connect, Disconnect or SetPath operations.  
Invalid data processor state.  
The request did not specify the length of its content, which is required by the requested resource.  
The maximum connection ID has been reached.  
A request method is not supported for the requested resource.  
This and all future requests should be directed to the given URI.  
The response to the request can be found under another URI using the GET method.  
Indicates multiple options for the resource from which the client may choose.  
The server successfully processed the request and is not returning any content.  
The server is a transforming proxy that received a WCL_E_SUCCESS from its origin, but is returning a modified version of the origin's response.  
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.  
An OBEX client is not connected to an OBEX server.  
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.  
The server either does not recognize the request method, or it lacks the ability to fulfill the request.  
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.  
An OBEX operation is in progress.  
The current operation has been terminated because a remote device is disconnected.  
The current operation has been terminated by a user.  
The server is delivering only part of the resource due to a range header sent by the client. The range header is used by OBEX clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.  
Reserved for future use.  
The server does not meet one of the preconditions that the requester put on the request.  
The client must first authenticate itself with the proxy.  
The server timed out waiting for the request.  
The request is larger than the server is willing or able to process.  
The server successfully processed the request, but is not returning any content. Unlike a WCL_E_OBEX_NO_CONTENT error, this error requires that the requester reset the object.  
The response to the request can be found under another URI using the GET method.  
The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. Also this error indicates that wrong Connect ID or Target used.  
Similar to WCL_E_OBEX_FORBIDDEN, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource.  
Unexpected or unknown OBEX result code.  
The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.  
The URI provided was too long for the server to process.  
The requested resource is available only through a proxy, the address for which is provided in the response.  
Copyright (c) 2006-2019. All rights reserved.