Re: WebServer on WinCE
- From: "John Spaith [MS]" <jspaith@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 14 Dec 2005 12:29:27 -0800
As long as the web server itself is running your COM object in its thread,
then it will not time you out automatically. If the web server is sitting
idle during a connection and the client goes 60 seconds without sending it
any data, that is when it will auto-timeout, but that's a different scenario
of course.
90 seconds is a rather long time so it's possible some client timeout may
kick in eventually, though this is a browser thing of course. The more
likely scenario is that a user may grow frustrated watching the little
waiting icon for a minute and a half so you'd definitely need some sort of
warning or maybe even a status or countdown bar of some sort.
--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation
Check out the new CE Networking Team Blog at http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.
"reinsch" <rdegenfellner@xxxxxxxxx> wrote in message
news:1134574248.814207.35700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I have a question on the CE Webserver. If I have a ASP page with a VB
> script that is doing some stuff with a COM object and let's say some
> function in the COM object would take like 90 seconds to execute, would
> that cause the webserver to not send the result of this ASP page to the
> client because of some timeout it hits.
> The question is, is there any kind of timeout the prevents the
> webserver from using to much time for the preparation of a asp page?
>
> thanks in advance
>
> regards
>
> Reinhold
>
.
- References:
- WebServer on WinCE
- From: reinsch
- WebServer on WinCE
- Prev by Date: Re: help with thunk implementation for armV4
- Next by Date: Re: Have the API's for menus changed in Windows Mobile 5.0
- Previous by thread: WebServer on WinCE
- Index(es):
Relevant Pages
|
|