File upload

[Kikoz]

Hi all.

I assume that if the user uploads a file from aspx page IIS will put all
future requests to the same page from other users in a line and all of them
will be waiting until this upload finishes. Meaning appl uses just one
thread for all requests. Right?

Is it safe or possible to get uploading request and execute it in a separate
thread safely saving the file in correct location on the server? Or anything
else? Articles, samples? I got a damn big traffic over here.

Thanks much for any help!
Kikoz

[Karl Seguin]

Kikoz:
It seems to me you are saying that when a user uploads a file, all of IIS
will lock out for all other requests on that page. IIS, like many web
servers, is a fully multi-threaded environment where each request is served
by a separate thread. Therefore there will not be any "waiting" as one
user uploads a file...only that user will be waiting - and that's because
his browser is on a single thread, he/she could open a new browser
window/tab and upload a 2nd file while the first one is uploading.

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Kikoz" <ki***@hotmail.com> wrote in message
news:uh**************@TK2MSFTNGP12.phx.gbl...

Hi all.

I assume that if the user uploads a file from aspx page IIS will put all
future requests to the same page from other users in a line and all of them will be waiting until this upload finishes. Meaning appl uses just one
thread for all requests. Right?

Is it safe or possible to get uploading request and execute it in a separate thread safely saving the file in correct location on the server? Or anything else? Articles, samples? I got a damn big traffic over here.

Thanks much for any help!
Kikoz

[Bill Borg]

Karl, this answers a similar question I've had about file uploads, thanks. Is
there any way to "demote" a thread like this--i.e. I want to make sure the
guy uploading a file is not bogging things down too badly for the interactive
users. I've been tempted to put the file upload code/data on a separate
server, but would prefer to keep it all together.

"Karl Seguin" wrote:

Kikoz:
It seems to me you are saying that when a user uploads a file, all of IIS
will lock out for all other requests on that page. IIS, like many web
servers, is a fully multi-threaded environment where each request is served
by a separate thread. Therefore there will not be any "waiting" as one
user uploads a file...only that user will be waiting - and that's because
his browser is on a single thread, he/she could open a new browser
window/tab and upload a 2nd file while the first one is uploading.

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Kikoz" <ki***@hotmail.com> wrote in message
news:uh**************@TK2MSFTNGP12.phx.gbl...

Hi all.

I assume that if the user uploads a file from aspx page IIS will put all
future requests to the same page from other users in a line and all of

them

will be waiting until this upload finishes. Meaning appl uses just one
thread for all requests. Right?

Is it safe or possible to get uploading request and execute it in a

separate

thread safely saving the file in correct location on the server? Or

anything

else? Articles, samples? I got a damn big traffic over here.

Thanks much for any help!
Kikoz

[Karl Seguin]

Bill,
Doubt I can properly answer you, you might want to start a new thread asking
the question again. I know that file uploads in ASP.Net aren't the "nicest"
thing...there used to be a memory deallocation bug in ASP.Net where memory
wasn't properly released...not sure if that's been fixed. You can read up
on it here: http://weblogs.asp.net/mhawley/archi...11/129824.aspx

I think right now your only two alternative is to write an ISAPI filter
(asp.net 2.0 should make this no longer necessary) or look at third party
components which behave better, such as ABCUpload that can save on the fly
to your HDD, thus leaving your precious RAM
intact...http://www.websupergoo.com/abcupload.net-1.htm

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Bill Borg" <Bi******@discussions.microsoft.com> wrote in message
news:70**********************************@microsof t.com...

Karl, this answers a similar question I've had about file uploads, thanks. Is there any way to "demote" a thread like this--i.e. I want to make sure the
guy uploading a file is not bogging things down too badly for the interactive users. I've been tempted to put the file upload code/data on a separate
server, but would prefer to keep it all together.

"Karl Seguin" wrote:

Kikoz:
It seems to me you are saying that when a user uploads a file, all of IIS will lock out for all other requests on that page. IIS, like many web
servers, is a fully multi-threaded environment where each request is served by a separate thread. Therefore there will not be any "waiting" as one user uploads a file...only that user will be waiting - and that's because his browser is on a single thread, he/she could open a new browser
window/tab and upload a 2nd file while the first one is uploading.

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Kikoz" <ki***@hotmail.com> wrote in message
news:uh**************@TK2MSFTNGP12.phx.gbl...

Hi all.

I assume that if the user uploads a file from aspx page IIS will put all future requests to the same page from other users in a line and all of

them

will be waiting until this upload finishes. Meaning appl uses just one
thread for all requests. Right?

Is it safe or possible to get uploading request and execute it in a

separate

thread safely saving the file in correct location on the server? Or

anything

else? Articles, samples? I got a damn big traffic over here.

Thanks much for any help!
Kikoz

[Kikoz]

Thanks, man.
"Karl Seguin" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME net>
wrote in message news:%2****************@TK2MSFTNGP14.phx.gbl...

Kikoz:
It seems to me you are saying that when a user uploads a file, all of IIS
will lock out for all other requests on that page. IIS, like many web
servers, is a fully multi-threaded environment where each request is
served
by a separate thread. Therefore there will not be any "waiting" as one
user uploads a file...only that user will be waiting - and that's because
his browser is on a single thread, he/she could open a new browser
window/tab and upload a 2nd file while the first one is uploading.

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Kikoz" <ki***@hotmail.com> wrote in message
news:uh**************@TK2MSFTNGP12.phx.gbl...

Hi all.

I assume that if the user uploads a file from aspx page IIS will put all
future requests to the same page from other users in a line and all of

them

will be waiting until this upload finishes. Meaning appl uses just one
thread for all requests. Right?

Is it safe or possible to get uploading request and execute it in a

separate

thread safely saving the file in correct location on the server? Or

anything

else? Articles, samples? I got a damn big traffic over here.

Thanks much for any help!
Kikoz

[Steve C. Orr [MVP, MCSD]]

SoftArtisans has several quality components to help smooth out uploads:
http://fileup.softartisans.com/fileup-131.aspx

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net
"Kikoz" <ki***@hotmail.com> wrote in message
news:uh**************@TK2MSFTNGP12.phx.gbl...

Hi all.

I assume that if the user uploads a file from aspx page IIS will put all
future requests to the same page from other users in a line and all of
them will be waiting until this upload finishes. Meaning appl uses just
one thread for all requests. Right?

Is it safe or possible to get uploading request and execute it in a
separate thread safely saving the file in correct location on the server?
Or anything else? Articles, samples? I got a damn big traffic over here.

Thanks much for any help!
Kikoz