Does ASP.NET wait for the entire request body before executing the ASP page?

[Peter Strøiman]

Hi.

I have an ASP page that will receive a lot of post data ( sometimes many
MB! ).
The ASP page processes the data sequentially, but does not need the entire
data stored in memory.

Therefore it is cruicial that executing the ASP page doesn't wait for the
entire request to arrive.
Then I would just begin to chunk my way through the Request.InputStream.

So my question is, will processing my ASP page begin before the entire
request has been received or not? Or is that something that can be
configured somewhere?

Thanks in advance,
Peter Strøiman

[Cowboy \(Gregory A. Beamer\)]

If you are dealing with streaming data, I would opt for a different
mechanism than an ASP page. WIthout understanding what you are trying to do,
I am in the dark as to how best to help you.

With a normal ASP.NET page, or ASP page for that matter, the Request is
small. The idea being that you are simply requesting a page, rather than
using the form send mechanism as a means of transfering large amounts of
data. Certainly, you can start Flushing the Response prior to grabbing the
data from the Request object, but an ASPX page is not the best data
receiver.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Peter Strøiman" <blah@blahblahblah> wrote in message
news:Os*************@tk2msftngp13.phx.gbl...

Hi.

I have an ASP page that will receive a lot of post data ( sometimes many
MB! ).
The ASP page processes the data sequentially, but does not need the entire
data stored in memory.

Therefore it is cruicial that executing the ASP page doesn't wait for the
entire request to arrive.
Then I would just begin to chunk my way through the Request.InputStream.

So my question is, will processing my ASP page begin before the entire
request has been received or not? Or is that something that can be
configured somewhere?

Thanks in advance,
Peter Strøiman

[Cowboy \(Gregory A. Beamer\)]

If you are dealing with streaming data, I would opt for a different
mechanism than an ASP page. WIthout understanding what you are trying to do,
I am in the dark as to how best to help you.

With a normal ASP.NET page, or ASP page for that matter, the Request is
small. The idea being that you are simply requesting a page, rather than
using the form send mechanism as a means of transfering large amounts of
data. Certainly, you can start Flushing the Response prior to grabbing the
data from the Request object, but an ASPX page is not the best data
receiver.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Peter Strøiman" <blah@blahblahblah> wrote in message
news:Os*************@tk2msftngp13.phx.gbl...

Hi.

I have an ASP page that will receive a lot of post data ( sometimes many
MB! ).
The ASP page processes the data sequentially, but does not need the entire
data stored in memory.

Therefore it is cruicial that executing the ASP page doesn't wait for the
entire request to arrive.
Then I would just begin to chunk my way through the Request.InputStream.

So my question is, will processing my ASP page begin before the entire
request has been received or not? Or is that something that can be
configured somewhere?

Thanks in advance,
Peter Strøiman

[Peter Strøiman]

Thanks for your reply.

I am dealing with streaming data. To be exact, I want to stream files ( +
some header information that I'll deal with - but disregard that for the
sake of argument. That's still just a part of the stream). Thus when my aspx
page receives the request, the data should be written to disk as it comes
in.
And I completely agrees with you that technically ASPX pages are not the
perfect choice. But it's a lot easier writing and debugging than creating a
windows service - which is the only alternative I can come to think of if I
want 24/7 operation.

But the question still is - will the page be executed before all the entire
request body has been received?

"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamM> wrote in
message news:OU**************@TK2MSFTNGP09.phx.gbl...

If you are dealing with streaming data, I would opt for a different
mechanism than an ASP page. WIthout understanding what you are trying to do, I am in the dark as to how best to help you.

With a normal ASP.NET page, or ASP page for that matter, the Request is
small. The idea being that you are simply requesting a page, rather than
using the form send mechanism as a means of transfering large amounts of
data. Certainly, you can start Flushing the Response prior to grabbing the
data from the Request object, but an ASPX page is not the best data
receiver.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Peter Strøiman" <blah@blahblahblah> wrote in message
news:Os*************@tk2msftngp13.phx.gbl...

Hi.

I have an ASP page that will receive a lot of post data ( sometimes many
MB! ).
The ASP page processes the data sequentially, but does not need the entire data stored in memory.

Therefore it is cruicial that executing the ASP page doesn't wait for the entire request to arrive.
Then I would just begin to chunk my way through the Request.InputStream.

So my question is, will processing my ASP page begin before the entire
request has been received or not? Or is that something that can be
configured somewhere?

Thanks in advance,
Peter Strøiman

[Peter Strøiman]

Thanks for your reply.

I am dealing with streaming data. To be exact, I want to stream files ( +
some header information that I'll deal with - but disregard that for the
sake of argument. That's still just a part of the stream). Thus when my aspx
page receives the request, the data should be written to disk as it comes
in.
And I completely agrees with you that technically ASPX pages are not the
perfect choice. But it's a lot easier writing and debugging than creating a
windows service - which is the only alternative I can come to think of if I
want 24/7 operation.

But the question still is - will the page be executed before all the entire
request body has been received?

"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamM> wrote in
message news:OU**************@TK2MSFTNGP09.phx.gbl...

If you are dealing with streaming data, I would opt for a different
mechanism than an ASP page. WIthout understanding what you are trying to do, I am in the dark as to how best to help you.

With a normal ASP.NET page, or ASP page for that matter, the Request is
small. The idea being that you are simply requesting a page, rather than
using the form send mechanism as a means of transfering large amounts of
data. Certainly, you can start Flushing the Response prior to grabbing the
data from the Request object, but an ASPX page is not the best data
receiver.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Peter Strøiman" <blah@blahblahblah> wrote in message
news:Os*************@tk2msftngp13.phx.gbl...

Hi.

I have an ASP page that will receive a lot of post data ( sometimes many
MB! ).
The ASP page processes the data sequentially, but does not need the entire data stored in memory.

Therefore it is cruicial that executing the ASP page doesn't wait for the entire request to arrive.
Then I would just begin to chunk my way through the Request.InputStream.

So my question is, will processing my ASP page begin before the entire
request has been received or not? Or is that something that can be
configured somewhere?

Thanks in advance,
Peter Strøiman