How can I end the HTTP response but continue executing ASP?

Hi there, when my ASP page receives the client request, I want to
gather the request data (form), promptly end the response to the
client (successful) and continue doing what I need to do with the
data, the result of which does not affect the response, hence why i
don't want to waste time leaving the connection open or keeping the
client waiting, I suppose you could call the client request a
"trigger".

I do not mind using ASP functions to fork, therad, execute or using
the buffer, whatever works... but I am very new to ASP/VBScript so I
do not know how to do this, and I think the Response.End will end ASP
execution, and I am not sure how to end only the HTTP response using
the buffer.

I don't want the client request to time out, I do not know the clients
time out settings.

I am not even sure if it is possible, perhaps it is a requirement of
ASP that the client waits for all ASP to execute, but there must be
some way, even using system calls or something to do this.

Thanks, George.

boole
Fri Feb 15 16:42:47 CST 2008

I would like to add, if I could somehow execute another ASP page from
the receiving page, telling it not to wait for execution to finsh
(like a fork), that would be ideal.

Anthony
Sat Feb 16 15:12:23 CST 2008



"boole" <geocoo@gmail.com> wrote in message
news:3d7d23ff-e4d6-46e4-80cb-752b573c0246@p43g2000hsc.googlegroups.com...
> Hi there, when my ASP page receives the client request, I want to
> gather the request data (form), promptly end the response to the
> client (successful) and continue doing what I need to do with the
> data, the result of which does not affect the response, hence why i
> don't want to waste time leaving the connection open or keeping the
> client waiting, I suppose you could call the client request a
> "trigger".
>
> I do not mind using ASP functions to fork, therad, execute or using
> the buffer, whatever works... but I am very new to ASP/VBScript so I
> do not know how to do this, and I think the Response.End will end ASP
> execution, and I am not sure how to end only the HTTP response using
> the buffer.
>
> I don't want the client request to time out, I do not know the clients
> time out settings.
>
> I am not even sure if it is possible, perhaps it is a requirement of
> ASP that the client waits for all ASP to execute, but there must be
> some way, even using system calls or something to do this.
>

> I would like to add, if I could somehow execute another ASP page from
> the receiving page, telling it not to wait for execution to finsh
> (like a fork), that would be ideal.

Since you are new to ASP is there anyway you can skip ASP altogether and
simply use ASP.NET instead? In ASP.NET its fairly straight forward to
instance a new thread to do your processing whilst allowing the response
handling thread to complete.

In ASP/VBScript (or any script for that matter) this sort of thing is not
possible.

My stock suggestion is to place the data you need for you processing in a
temporary DB table or in an XML file. You can then have a scheduled task
monitor the table or folder where the XML is placed and have it process the
record. If you prefer you could have it post to an ASP page telling it what
record or file to process.

--
Anthony Jones - MVP ASP/ASP.NET

Jon
Sun Feb 17 10:33:54 CST 2008

you may want to place your processing code into a COM script component.

learn more here:

http://www.microsoft.com/mspress/books/sampchap/1394b.aspx

Anthony
Sun Feb 17 15:21:17 CST 2008

"Jon Paal [MSMD]" <Jon nospam Paal @ everywhere dot com> wrote in message
news:13rgofl7as0o898@corp.supernews.com...
> you may want to place your processing code into a COM script component.
>
> learn more here:
>
> http://www.microsoft.com/mspress/books/sampchap/1394b.aspx
>
>


That in itself won't allow the ASP script to return to the client before
processing is complete.
Calls into a component from ASP are synchronous. A compiled component can
obviously use an additional thread to continue processing whilst allowing
the called to thread to return. However coding this properly involves
considerable complexity.


--
Anthony Jones - MVP ASP/ASP.NET