Hi,

My Name is Nasir Hussain, I am facing a problem while using custom

component. Can anybody help me to rtesolve 

In ASP page, if we call a method of a component and are waiting for its

result.Can we make a check that our custom commponent if does not response

for 2 min. then we should stop waiting for the result from controll.



Thanks,

Nasir Hussain

nasirmalik@s...

Even if you could do this, two minutes is surely a long time to wait for

any page to load. HTTP is stateless: it and doesn't provide a way of doing

callback notifications to the client's browser, so any component that

provides the presentation layer should really be capable of processing its

call and then handing its responses straight back to the HTTP request more

or less straight away. Trying to trap-out components that might take an

unacceptable time to process their work is perhaps the wrong approach, and

looping on the server to check for a status flag from your component

dosen't scale well either. You might want to solve this via Message

Queuing and running your business logic in using background processing.

There's an excellent article here by Chris Blexrud:

http://www.asptoday.com/articles/19990727.htm



Daniel Walker

Wrox Press



> Hi,

> My Name is Nasir Hussain, I am facing a problem while using custom

> component. Can anybody help me to rtesolve 

> In ASP page, if we call a method of a component and are waiting for its

> result.Can we make a check that our custom commponent if does not response

> for 2 min. then we should stop waiting for the result from controll.

> 

> Thanks,

> Nasir Hussain

> nasirmalik@s...