The Timeout property on HttpWebRequest is the timeout for a single receive,
send, dial, or connect request, and not for the entire request processing
time. If the request is still executing, that means that it is still
making progress in completing the request.
Hope this helps.
Mike Boilen
Developer
.NET Compact Framework
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.gotdotnet.com/team/netcf/FAQ.aspx
--------------------
| From: "Zen" <
[email protected]>
| Subject: SSL is slow on PocketPC2000 via Cradle
| Date: Wed, 20 Aug 2003 12:29:16 -0500
| Lines: 8
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
| Message-ID: <
[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| NNTP-Posting-Host: outbound.epicsys.com 12.148.194.126
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:31445
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| I have to set the Timeout for the initial SSL connection to be 100 seconds
| to not hit the timeout error.
|
| Is there any other way around it? Is there a patch for PocketPC2000?
|
| Thanks a lot!
|
|
|