Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. Stateful ASP.NET Application

Stateful ASP.NET Application

Scheduled Pinned Locked Moved ASP.NET
helpquestioncsharpasp-netdatabase
7 Posts 4 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I Offline
    I Offline
    islam sayed
    wrote on last edited by
    #1

    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

    A A 2 Replies Last reply
    0
    • I islam sayed

      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

      A Offline
      A Offline
      Alvaro Mendez
      wrote on last edited by
      #2

      I think you need to rethink your web client implementation. It's not meant to be directly connected to a server all the time. That's why one server is able to serve thousands of clients. The server may certainly keep track of each user (via the Session), but the connection is dropped every time the page is sent back. You may want to adopt a different architecture, whereby all COM events are sent to a queue and whenever the client makes a new request, check what events are in the queue and notify the user accordingly. Regards, Alvaro


      You know what they say about arguing over the Internet...

      I 1 Reply Last reply
      0
      • A Alvaro Mendez

        I think you need to rethink your web client implementation. It's not meant to be directly connected to a server all the time. That's why one server is able to serve thousands of clients. The server may certainly keep track of each user (via the Session), but the connection is dropped every time the page is sent back. You may want to adopt a different architecture, whereby all COM events are sent to a queue and whenever the client makes a new request, check what events are in the queue and notify the user accordingly. Regards, Alvaro


        You know what they say about arguing over the Internet...

        I Offline
        I Offline
        islam sayed
        wrote on last edited by
        #3

        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...

        I 1 Reply Last reply
        0
        • I islam sayed

          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...

          I Offline
          I Offline
          islam sayed
          wrote on last edited by
          #4

          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 ?

          1 Reply Last reply
          0
          • I islam sayed

            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

            A Offline
            A Offline
            Anushu
            wrote on last edited by
            #5

            Hi, Hope the following few references would help in answering your questions, give them a try 316516 How To Sink Managed Visual Basic .NET Events in Internet Explorer Script http://support.microsoft.com/?id=316516 316510 PRB: Security Exception When You Use Event Handlers in Internet Explorer http://support.microsoft.com/?id=316510 814664 PRB: ActiveX Error When You Sink Managed Events in Internet Explorer http://support.microsoft.com/?id=814664

            I 1 Reply Last reply
            0
            • A Anushu

              Hi, Hope the following few references would help in answering your questions, give them a try 316516 How To Sink Managed Visual Basic .NET Events in Internet Explorer Script http://support.microsoft.com/?id=316516 316510 PRB: Security Exception When You Use Event Handlers in Internet Explorer http://support.microsoft.com/?id=316510 814664 PRB: ActiveX Error When You Sink Managed Events in Internet Explorer http://support.microsoft.com/?id=814664

              I Offline
              I Offline
              islam sayed
              wrote on last edited by
              #6

              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 ?

              A 1 Reply Last reply
              0
              • I islam sayed

                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 ?

                A Offline
                A Offline
                Anonymous
                wrote on last edited by
                #7

                Active X controls. i think they would try to get loaded on to the client and check for registry.. usual COM stuff... i think it would require some wrapper for managed

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • World
                • Users
                • Groups