Sequential one request at a time processing

ASP.NET processes one request at a time, sequentially. If one process
blocks or sleeps then it brings down the entire application for all
users.

This fact is hidden under the rug by Microsoft. It would clearly be a
problem for any website that has tons of traffic.

On this I seek specifics.

Is it sequential per DLL or per page? If one page blocks, on say a big
database query, will other pages process and respond?

On a multi-processor server, say with four processors, is this still a
problem? Or will each processor be independent of eachother?

How does this sequential processing scale to a web farm or garden?

Thanks for your help.asp.net does not process pages sequential, it can currenlty process as many
requests as the thread pool size. if your pages are processing sequentialy,
then you have put code on your pages that blocks.

-- bruce (sqlwork.com)

"Bruce W.1" <no@.direct.email> wrote in message
news:4023BDDA.57A8DAAF@.direct.email...
> ASP.NET processes one request at a time, sequentially. If one process
> blocks or sleeps then it brings down the entire application for all
> users.
> This fact is hidden under the rug by Microsoft. It would clearly be a
> problem for any website that has tons of traffic.
> On this I seek specifics.
> Is it sequential per DLL or per page? If one page blocks, on say a big
> database query, will other pages process and respond?
> On a multi-processor server, say with four processors, is this still a
> problem? Or will each processor be independent of eachother?
> How does this sequential processing scale to a web farm or garden?
> Thanks for your help.
bruce barker wrote:
> asp.net does not process pages sequential, it can currenlty process as many
> requests as the thread pool size. if your pages are processing sequentialy,
> then you have put code on your pages that blocks.
> -- bruce (sqlwork.com)
================================================== ======

Wrong. Test it yourself.

When a page blocks, for whatever reason, other requests to the page are
not processed.

Serve ASP.NET control through custom RequestHandler

Hi NG,
Is it possible in any way to serve an ASP.NET server control when the
request is beeing processed by a custom request handler?
In my case I use my own request handler to serve elements that exists as
content in a database, and not as files in the file system. What i want is
to be able to place ASP.NET controls on some of my output, so they can be
served alongside my requested content.
I've tried to create a System.Web.UI.Page instance, add a HtmlForm to its
Controls collection and my ASP.NET control to the HtmlForm. Calling the
Control or Page RenderControl() method provided me with the initial output
of the control, but it seams i need to do a little more work than that.
The Viewstate isn't maintained and the serverside events generated by the
control cannot be caught.
Do I need to manually parse the request for viewstate and serverside events?
Is there a way to do this easily? Or do I end up making my own version of
the ASP.NET RequestHandler?
Could anyone point me in the right direction?
Thanks for your time,
Ricky"Ricky K. Rasmussen" <morten@.mvponline.dk> wrote in message
news:eyNw%236HTEHA.332@.TK2MSFTNGP11.phx.gbl...
> Hi NG,
> Is it possible in any way to serve an ASP.NET server control when the
> request is beeing processed by a custom request handler?
> In my case I use my own request handler to serve elements that exists as
> content in a database, and not as files in the file system. What i want is
> to be able to place ASP.NET controls on some of my output, so they can be
> served alongside my requested content.
> I've tried to create a System.Web.UI.Page instance, add a HtmlForm to its
> Controls collection and my ASP.NET control to the HtmlForm. Calling the
> Control or Page RenderControl() method provided me with the initial output
> of the control, but it seams i need to do a little more work than that.
> The Viewstate isn't maintained and the serverside events generated by the
> control cannot be caught.
> Do I need to manually parse the request for viewstate and serverside
events?
> Is there a way to do this easily? Or do I end up making my own version of
> the ASP.NET RequestHandler?
> Could anyone point me in the right direction?
If your handler is able to derive from System.Web.UI.Page, then it will _be_
a page, and everything should work.
--
John Saunders
johnwsaundersiii at hotmail
Thanks for your reply John.
I know that deriving from the System.Web.UI.Page creates a ASP.NET Page that
can be served throug the ASP.NET RequestHandler. But what I want to do is to
serve an ASP.NET WebControl throug my own RequestHandler.
I figure this means that I need to programatically create a
System.Web.UI.Page with a HtmlForm containing my control, and then serve the
Page... but how do I do this?
Calling Page.RenderControl() does only create the initial output and doesn't
parse the request for server events and viewstate. Is there a way for me to
make the Page work as if it was served through the ASP.NET RequestHandler?
Thank you for your time,
Ricky
"John Saunders" <johnwsaundersiii@.notcoldmail.com> wrote in message
news:u19k0WITEHA.1544@.TK2MSFTNGP09.phx.gbl...
> If your handler is able to derive from System.Web.UI.Page, then it will
_be_
> a page, and everything should work.
> --
> John Saunders
> johnwsaundersiii at hotmail
>
"Ricky K. Rasmussen" <morten@.mvponline.dk> wrote in message
news:uyrRW9ITEHA.1232@.TK2MSFTNGP09.phx.gbl...
> Thanks for your reply John.
> I know that deriving from the System.Web.UI.Page creates a ASP.NET Page
that
> can be served throug the ASP.NET RequestHandler. But what I want to do is
to
> serve an ASP.NET WebControl throug my own RequestHandler.
> I figure this means that I need to programatically create a
> System.Web.UI.Page with a HtmlForm containing my control, and then serve
the
> Page... but how do I do this?
> Calling Page.RenderControl() does only create the initial output and
doesn't
> parse the request for server events and viewstate. Is there a way for me
to
> make the Page work as if it was served through the ASP.NET RequestHandler?
No, I meant that your HttpHandler should _be_ a page:
public class MyRequestHandler : System.Web.UI.Page
{
...
}
John Saunders
johnwsaundersiii at hotmail

Serve ASP.NET control through custom RequestHandler

Hi NG,

Is it possible in any way to serve an ASP.NET server control when the
request is beeing processed by a custom request handler?

In my case I use my own request handler to serve elements that exists as
content in a database, and not as files in the file system. What i want is
to be able to place ASP.NET controls on some of my output, so they can be
served alongside my requested content.

I've tried to create a System.Web.UI.Page instance, add a HtmlForm to its
Controls collection and my ASP.NET control to the HtmlForm. Calling the
Control or Page RenderControl() method provided me with the initial output
of the control, but it seams i need to do a little more work than that.

The Viewstate isn't maintained and the serverside events generated by the
control cannot be caught.

Do I need to manually parse the request for viewstate and serverside events?
Is there a way to do this easily? Or do I end up making my own version of
the ASP.NET RequestHandler?

Could anyone point me in the right direction?

Thanks for your time,
Ricky"Ricky K. Rasmussen" <morten@.mvponline.dk> wrote in message
news:eyNw%236HTEHA.332@.TK2MSFTNGP11.phx.gbl...
> Hi NG,
> Is it possible in any way to serve an ASP.NET server control when the
> request is beeing processed by a custom request handler?
> In my case I use my own request handler to serve elements that exists as
> content in a database, and not as files in the file system. What i want is
> to be able to place ASP.NET controls on some of my output, so they can be
> served alongside my requested content.
> I've tried to create a System.Web.UI.Page instance, add a HtmlForm to its
> Controls collection and my ASP.NET control to the HtmlForm. Calling the
> Control or Page RenderControl() method provided me with the initial output
> of the control, but it seams i need to do a little more work than that.
> The Viewstate isn't maintained and the serverside events generated by the
> control cannot be caught.
> Do I need to manually parse the request for viewstate and serverside
events?
> Is there a way to do this easily? Or do I end up making my own version of
> the ASP.NET RequestHandler?
> Could anyone point me in the right direction?

If your handler is able to derive from System.Web.UI.Page, then it will _be_
a page, and everything should work.
--
John Saunders
johnwsaundersiii at hotmail
Thanks for your reply John.

I know that deriving from the System.Web.UI.Page creates a ASP.NET Page that
can be served throug the ASP.NET RequestHandler. But what I want to do is to
serve an ASP.NET WebControl throug my own RequestHandler.

I figure this means that I need to programatically create a
System.Web.UI.Page with a HtmlForm containing my control, and then serve the
Page... but how do I do this?

Calling Page.RenderControl() does only create the initial output and doesn't
parse the request for server events and viewstate. Is there a way for me to
make the Page work as if it was served through the ASP.NET RequestHandler?

Thank you for your time,
Ricky

"John Saunders" <johnwsaundersiii@.notcoldmail.com> wrote in message
news:u19k0WITEHA.1544@.TK2MSFTNGP09.phx.gbl...
> If your handler is able to derive from System.Web.UI.Page, then it will
_be_
> a page, and everything should work.
> --
> John Saunders
> johnwsaundersiii at hotmail
"Ricky K. Rasmussen" <morten@.mvponline.dk> wrote in message
news:uyrRW9ITEHA.1232@.TK2MSFTNGP09.phx.gbl...
> Thanks for your reply John.
> I know that deriving from the System.Web.UI.Page creates a ASP.NET Page
that
> can be served throug the ASP.NET RequestHandler. But what I want to do is
to
> serve an ASP.NET WebControl throug my own RequestHandler.
> I figure this means that I need to programatically create a
> System.Web.UI.Page with a HtmlForm containing my control, and then serve
the
> Page... but how do I do this?
> Calling Page.RenderControl() does only create the initial output and
doesn't
> parse the request for server events and viewstate. Is there a way for me
to
> make the Page work as if it was served through the ASP.NET RequestHandler?

No, I meant that your HttpHandler should _be_ a page:

public class MyRequestHandler : System.Web.UI.Page
{
...
}

--
John Saunders
johnwsaundersiii at hotmail

Server Application Error

Server Application Error.
The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance.
I am getting this error when i pass the url http://localhost/
The operating system was windowsxpsp2,IE6.0.2900.
Please give me the suggestion.What does the event log say about the error. It should be more detailed. to get to the event log right click "My Computer", click "Manage". Go to "Event Viewer". Not sure which log it shows up in. Look for the date and time it happened.

hello mlogan...

thank u for ur suggestion. but i formatted the OS.

bye...