MrTT20
August 30th, 2005, 05:52 AM
Hi, :wave:
on the server side of my asp.net web-app, i need to instantiate a com component and invoke some methods on it (e.g. Login()). After that i have to wait for an Event fired by the com-component (e.g. wait for an USER_LOGIN_SUCCESS). During that time i need to wait on the server (Page-File) and block the request.
I generated the Runtime Callable Wrapper and registered the Event on class that encapsulates the component. The Event-Handler sets the boolean "logonCompleted" to "true" and the blocking is implemented by the following code:
while(!logonCompleted){
System.Threading.Thread.Sleep(1000);
}
Is there any other (better) solution for that problem. I think this code would cause some big performance and scalability issues because each Page-instance is handled by the same Thread. Did anybody else have some experiences with that problem?
Thank you for participating.
best regards,
lars
on the server side of my asp.net web-app, i need to instantiate a com component and invoke some methods on it (e.g. Login()). After that i have to wait for an Event fired by the com-component (e.g. wait for an USER_LOGIN_SUCCESS). During that time i need to wait on the server (Page-File) and block the request.
I generated the Runtime Callable Wrapper and registered the Event on class that encapsulates the component. The Event-Handler sets the boolean "logonCompleted" to "true" and the blocking is implemented by the following code:
while(!logonCompleted){
System.Threading.Thread.Sleep(1000);
}
Is there any other (better) solution for that problem. I think this code would cause some big performance and scalability issues because each Page-instance is handled by the same Thread. Did anybody else have some experiences with that problem?
Thank you for participating.
best regards,
lars