Cross Reference: /packages/apps/Exchange/src/com/android/exchange/EasSyncService.java

Lines Matching refs:timeout
128     // Command timeout is the the time allowed for reading data from an open connection before an
132     // Connection timeout is the time given to connect to the server before reporting an IOException
157      * We start with an 8 minute timeout, and increase/decrease by 3 minutes at a time.  There's
158      * no point having a timeout shorter than 5 minutes, I think; at that point, we can just let
163      * If we ever have to drop the ping timeout, we'll never increase it again.  There's no point
164      * going into hysteresis; the NAT timeout isn't going to change without a change in connection,
268      * socket timeout without having thrown an Exception
934      * TODO: shorter timeout for interactive lookup
1250     private HttpClient getHttpClient(int timeout) {
1253         HttpConnectionParams.setSoTimeout(params, timeout);
1270            userLog("Send ping, timeout: " + heartbeat + "s, high: " + mPingHighWaterMark + 's');
1278     protected EasResponse executePostWithTimeout(HttpClient client, HttpPost method, int timeout)
1280         return executePostWithTimeout(client, method, timeout, false);
1284      * Handle executing an HTTP POST command with proper timeout, watchdog, and ping behavior
1287      * @param timeout the timeout before failure, in ms
1292     protected EasResponse executePostWithTimeout(HttpClient client, HttpPost method, int timeout,
1296             long alarmTime = timeout + WATCHDOG_TIMEOUT_ALLOWANCE;
1317     public EasResponse sendHttpClientPost(String cmd, HttpEntity entity, int timeout)
1319         HttpClient client = getHttpClient(timeout);
1353         return executePostWithTimeout(client, method, timeout, isPingCommand);
1910      * Simplistic attempt to determine a NAT timeout, based on experience with various carriers
2026                     // Send the ping, wrapped by appropriate timeout/alarm
2057                                 // not at the maximum, try increasing timeout by two minutes
2089                     // If we get the exception that is indicative of a NAT timeout and if we
2090                     // haven't yet "fixed" the timeout, back off by two minutes and "fix" it
2319             // Start with the default timeout
2320             int timeout = COMMAND_TIMEOUT;
2329                 // Use enormous timeout for initial sync, which empirically can take a while longer
2330                 timeout = 120*SECONDS;
2343                     timeout);