version 1.24, 2006/01/31 16:07:38
|
version 1.24.2.2, 2007/03/07 20:54:32
|
|
|
virtual void setTimeout(Uint32 timeoutMilliseconds) | virtual void setTimeout(Uint32 timeoutMilliseconds) |
{ | { |
_timeoutMilliseconds = timeoutMilliseconds; | _timeoutMilliseconds = timeoutMilliseconds; |
|
if ((_connected) && (_httpConnection != 0)) |
|
_httpConnection->setSocketWriteTimeout(_timeoutMilliseconds/1000+1); |
} | } |
| |
// l10n start | // l10n start |
|
|
| |
void _disconnect(); | void _disconnect(); |
| |
void _reconnect(); |
|
|
|
Message* _doRequest( | Message* _doRequest( |
AutoPtr<CIMRequestMessage>& request, | AutoPtr<CIMRequestMessage>& request, |
const Uint32 expectedResponseMessageType); | const Uint32 expectedResponseMessageType); |
|
|
| |
Uint32 _timeoutMilliseconds; | Uint32 _timeoutMilliseconds; |
Boolean _connected; | Boolean _connected; |
|
/** |
|
The CIMClient uses a lazy reconnect algorithm. A reconnection |
|
is necessary when the server (listener) sends a Connection: Close |
|
header in the HTTP response or when a connection timeout occurs |
|
while waiting for a response. In these cases, a disconnect is |
|
performed immediately and the _doReconnect flag is set. The |
|
connection is re-established only when required to perform another |
|
operation. Note that in the case of a connection timeout, the |
|
challenge status must be reset in the ClientAuthenticator to allow |
|
authentication to be performed properly on the new connection. |
|
*/ |
|
Boolean _doReconnect; |
|
|
AutoPtr<CIMOperationResponseDecoder> _responseDecoder; | AutoPtr<CIMOperationResponseDecoder> _responseDecoder; |
AutoPtr<CIMOperationRequestEncoder> _requestEncoder; | AutoPtr<CIMOperationRequestEncoder> _requestEncoder; |
ClientAuthenticator _authenticator; | ClientAuthenticator _authenticator; |