thanks i will check that , seems interesting stuff I am now actually thinking of a solution that could be useful, need your opinion guys as well. What about doing the whole thing as an ActiveX Control ? and host the control in an ASP.NET application form ? In The ActiveX Control Logic , i guess i would be connected all the time to my COM server , and also would be able to sink events ... suggesstions ?

about the Timer component in ASP.net . does it send the event Time_Elapsed in ASP.NET. I tried and seems it raises the event, although after the page has already been supplied to the client. This means what ?

thank you for reply. exactly as i was thinking the idea of queue.it is acceptable to me , but what application would host that queue ? .net remoting service ? how...

Hi Everyone, This is my first post in here , and thank you for the great efforts. I am stuck with a problem and any opinions on how best it could be solved is highly appreciated. I have a COM library that interacts with an external database.It pulls events from the database and present it to COM clients.This should now work from a web application. I need the client to be notified of events coming from the COM library , so it should always be connected or the server would lose reference and the client is gone.I also need to persist this connectivity throughout calls. What is the best solution to go to solve this problem ? Is this actually possible in Asp.NET ? or would i go to a different technology ? I couldnt find a clue but i feel it has a simple solution right at hand that i am not aware of. I have ideas about doing a service and client for every session connected at all times using .NET Remoting but seems daunting to start implementing this without a good reason. All your ideas and discussions are welcomed. Thank You