Namespaces | |
Activity | |
Base | |
Dns | |
Exchange | |
Graph | |
Imap | |
Pop3 | |
Smtp | |
Classes | |
class | AsyncCommandResultEventArgs |
AsyncCommandResultEventArgs is containing event data. More... | |
class | CommandStatus |
Indicates the result of an operation. More... | |
class | Details_NetworkException |
Thrown if there is a network connection failure. More... | |
class | EmailClient |
Represents the client that creates server connection by using the host credentials. More... | |
class | HttpProxy |
HTTP proxy client. More... | |
class | IAsyncResultExt |
Represents the extended status of an asynchronous operation. More... | |
class | ICommand |
Defines a command. More... | |
class | IConnection |
IConnectionAdapter allows to manage connection to a server. More... | |
class | IMultipleServicesTokenProvider |
Defines interface allowing to retrieve access token. More... | |
class | ITokenProvider |
Defines interface allowing to retrieve access token. More... | |
class | MessageInfoBase |
The MessageInfo represents the E-Mail message info fetched from the mail server. More... | |
class | NameValuePair |
An extended property. More... | |
class | OAuthNetworkCredential |
Represents the NetworkCredential for OAuth authentication. More... | |
class | OAuthToken |
Contains OAuth token data such like token value, token type, expiration date. More... | |
class | PageInfo |
Contains information about retrieved page when paging methods are used. More... | |
class | PipeliningStatus |
Defines pipelining status for mail client. More... | |
class | Proxy |
Base proxy client. More... | |
class | SecurityOptionsExtensions |
class | SocksProxy |
SOCKS proxy client. Supported versions of the protocol are SOCKS4 and SOCKS5. More... | |
class | TokenProvider |
Class TokenProvider allows to retrieve access token for mail services. More... | |
Typedefs | |
using | BindIPEndPointHandler = System::MulticastDelegate< System::SharedPtr< System::Net::IPEndPoint >(System::SharedPtr< System::Net::IPEndPoint >)> |
using | NetworkException = System::ExceptionWrapper< Details_NetworkException > |
using Aspose::Email::Clients::BindIPEndPointHandler = typedef System::MulticastDelegate<System::SharedPtr<System::Net::IPEndPoint>(System::SharedPtr<System::Net::IPEndPoint>)> |
using Aspose::Email::Clients::NetworkException = typedef System::ExceptionWrapper<Details_NetworkException> |
|
strong |
|
strong |
|
strong |
Defines algorithm of connection allocation in multiple threads environment
Enumerator | |
---|---|
UseMainOrDefault | This mode uses by default in email clients. Email client uses main connection for all operations from multiple threads if default connection hasn't been created, or connection hasnt been passed as method parameter explicitly. Main connection is connection which is created in the same time like email client. User can create default connections for threads with CreateConnection method. If default connection for thread is created, it's used implicitly for all methods of email client which are invoked in this thread. If default connection for thread is not created, main connection is used for all methods of email client which are invoked in this thread. User also can create independent connections not linked with threads (not default connections) with CreateConnection method. If user wants to use other connections (not main and not default) he has to pass this connection explicitly as parameter of a method which he wants to use. User can additionally create any number of connections. Default connection can be only one per thread. Please note default connections works correctly if user uses Thread objects for multitasking programming. If user uses ConnectionPool or uses Task objects for multitasking programming this mode may lead to wrong behaviour of a programm because of thread may be reused in this case. To avoid this problem user has to manually dispose default conection (if he uses it) in the end of the code which executes in the thread. |
UseMain | Email client uses main connection for all operations from multiple threads. Main connection is connection which is created in the same time like email client. User cann't create default connections. User can create independent connections not linked with threads (not default connections) with CreateConnection method. If user wants to use other connections (not main and not default) he has to pass this connection explicitly as parameter of a method which he wants to use. User can additionally create any number of connections. |
UseDefault | Email client uses implicitly only default connections for all operations from multiple threads. Main connection is not used in this mode. If default connection hasn't been created for some thread (first invocation of email client method), email client creates default connection implicitly for thread before first operation is executed. User can't create default connections for threads with CreateConnection method because they are created automatically. When default connection for thread is created, it's used implicitly for all methods of email client which are invoked in this thread.read. User also can create independent connections not linked with threads (not default connections) with CreateConnection method. If user wants to use other connections (not main and not default) he has to pass this connection explicitly as parameter of a method which he wants to use. User can additionally create any number of connections. Default connection can be only one per thread. Please note default connections works correctly if user uses Thread objects for multitasking programming. If user uses ConnectionPool or uses Task objects for multitasking programming this mode may lead to wrong behaviour of a programm because of thread may be reused in this case. To avoid this problem user has to manually dispose default conection in the end of the code which executes in the thread. |
|
strong |
|
strong |
|
strong |
|
strong |
|
strong |
|
strong |
|
strong |
Versions of the SOCKS protocol
|
strong |