"Steven Cheng[MSFT]" <stcheng@online.microsoft.com> wrote in message
news:F0$fQn$xFHA.3372@TK2MSFTNGXA01.phx.gbl...
> Hi Alan,
>
> How are you doing on this issue, does the suggestion in my last reply help
> a little? If there're anything else we can help, please feel free to post
> here. Thanks,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
> --------------------
> X-Tomcat-ID: 31610486
> References: <elwsDlCxFHA.3812@TK2MSFTNGP09.phx.gbl>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="----=_NextPart_0001_001C530A"
> Content-Transfer-Encoding: 7bit
> From: stcheng@online.microsoft.com (Steven Cheng[MSFT])
> Organization: Microsoft
> Date: Thu, 29 Sep 2005 02:00:22 GMT
> Subject: RE: Timeout value at the client proxy
> X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
> Message-ID: <jY7vbmJxFHA.780@TK2MSFTNGXA01.phx.gbl>
> Newsgroups: microsoft.public.dotnet.framework.webservices
> Lines: 105
> Path: TK2MSFTNGXA01.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.dotnet.framework.webservices:8053
> NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
>
> Hi Alan,
>
> Welcome to Webservice newsgroup.
> Regarding on the configuring HTTP timeout in clientside question, based on
> my understanding, HTTP Timeout setting is generally available on
> serverside
> , by IIS's script timeout configuration or ASP.NET' httpruntime
> executionTimeout setting. For clientside, there is no such timeout
> setting
> specific to http protocol request. If you're using the .NET framework
> generated webservice client proxy, we can configure the webservice's
> method
> call Timeout through the
> SoapHttpClientProtocol.Timeout property
>
> But this property only affect the clientside timeout waiting for a
> webmethod call (synchronous), it won't have any effect on the serverside
> 's
> service processing timeout).
>
> Thanks,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
>
>
>
>
>
> --------------------
> From: "A.M-SG" <alanalan@newsgroup.nospam>
> Subject: Timeout value at the client proxy
> Date: Wed, 28 Sep 2005 08:36:35 -0400
> Lines: 8
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> X-RFC2646: Format=Flowed; Original
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> Message-ID: <elwsDlCxFHA.3812@TK2MSFTNGP09.phx.gbl>
> Newsgroups: microsoft.public.dotnet.framework.webservices
> NNTP-Posting-Host: hse-toronto-ppp137724.sympatico.ca 64.228.95.207
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.dotnet.framework.webservices:8046
> X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
>
> Hi,
>
> How can I increase the HTTP Timeout value at the client side?
>
> Thank you,
> Alan
>
>
>
>