Allowing applications to "listen in" to my app

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Andrew Ducker

    Allowing applications to "listen in" to my app

    I have an application, and I'd like it to be able to generate "log"
    messages. Other applications can then attach to it and listen to
    these messages, but the main application shouldn't have to worry about
    how many other apps are listening in, what they do with the messages,
    etc.

    Can I do this with Remoting?

    Cheers,

    Andy
  • Andrew Ducker

    #2
    Re: Allowing applications to "listen in" to my app

    On 5 May, 12:26, Andrew Ducker <and...@ducker. org.ukwrote:
    I have an application, and I'd like it to be able to generate "log"
    messages. Other applications can then attach to it and listen to
    these messages, but the main application shouldn't have to worry about
    how many other apps are listening in, what they do with the messages,
    etc.
    >
    Can I do this with Remoting?
    As a connected thought - can I connect to the Debug.Listeners of an
    application from a separate app?

    Cheers,

    Andy

    Comment

    • Marcin Hoppe

      #3
      Re: Allowing applications to &quot;listen in&quot; to my app

      Andrew Ducker pisze:
      I have an application, and I'd like it to be able to generate "log"
      messages. Other applications can then attach to it and listen to
      these messages, but the main application shouldn't have to worry about
      how many other apps are listening in, what they do with the messages,
      etc.
      Take a look at log4net. Once you have instrumented your code with trace
      statements, you can configure it to write messages to many outputs,
      oneof them being multicast UDP datagrams. It is also possible to set it
      up in such a way that clients can connect via telnet to your process and
      listen to messages.

      Best regards!
      --
      Marcin Hoppe
      Email: marcin.hoppe@gm ail.com
      Blog: http://devlicio.us/blogs/marcin_hoppe

      Comment

      • parez

        #4
        Re: Allowing applications to &quot;listen in&quot; to my app

        On May 5, 8:42 am, Andrew Ducker <and...@ducker. org.ukwrote:
        On 5 May, 12:26, Andrew Ducker <and...@ducker. org.ukwrote:
        >
        I have an application, and I'd like it to be able to generate "log"
        messages. Other applications can then attach to it and listen to
        these messages, but the main application shouldn't have to worry about
        how many other apps are listening in, what they do with the messages,
        etc.
        >
        Can I do this with Remoting?
        >
        As a connected thought - can I connect to the Debug.Listeners of an
        application from a separate app?
        >
        Cheers,
        >
        Andy
        I THINK it mite be possible by doing the following

        your main app writes to a msmq queue.
        other applications : poll and peek the queue with cursor.

        Comment

        • Marcin Hoppe

          #5
          Re: Allowing applications to &quot;listen in&quot; to my app

          parez pisze:
          your main app writes to a msmq queue.
          While this is of course a viable solution, I would not recommend it. My
          experience with MSMQ is that this is a high maintenance technology and
          not super easy to set up.

          --
          Marcin Hoppe
          Email: marcin.hoppe@gm ail.com
          Blog: http://devlicio.us/blogs/marcin_hoppe

          Comment

          • parez

            #6
            Re: Allowing applications to &quot;listen in&quot; to my app

            On May 5, 1:42 pm, Marcin Hoppe <marcin.ho...@g mail.comwrote:
            parez pisze:
            >
            your main app writes to a msmq queue.
            >
            While this is of course a viable solution, I would not recommend it. My
            experience with MSMQ is that this is a high maintenance technology and
            not super easy to set up.
            >
            --
            Marcin Hoppe
            Email: marcin.ho...@gm ail.com
            Blog:http://devlicio.us/blogs/marcin_hoppe
            I really havent had problems with MSMQ. But experience is limited to
            2 applications. (one high volume and one low volume). The only thing
            that took a while was getting the queue name right..

            I looked into log4net.. that might be the way to go.. as there is no
            need to re-invent the wheel. it even has MSMQ appender..

            Comment

            • =?ISO-8859-1?Q?Arne_Vajh=F8j?=

              #7
              Re: Allowing applications to &quot;listen in&quot; to my app

              Andrew Ducker wrote:
              I have an application, and I'd like it to be able to generate "log"
              messages. Other applications can then attach to it and listen to
              these messages, but the main application shouldn't have to worry about
              how many other apps are listening in, what they do with the messages,
              etc.
              You need an observer or publish-subscribe model.
              Can I do this with Remoting?
              Yes. But I think it will be a clumsy tool for the task.

              Plain sockets will probably fit better.

              Or the message queue solution.

              Arne

              Comment

              • =?ISO-8859-1?Q?Arne_Vajh=F8j?=

                #8
                Re: Allowing applications to &quot;listen in&quot; to my app

                Marcin Hoppe wrote:
                parez pisze:
                >your main app writes to a msmq queue.
                >
                While this is of course a viable solution, I would not recommend it. My
                experience with MSMQ is that this is a high maintenance technology and
                not super easy to set up.
                I have never worked with MSMQ - only MQSeries and AMQ, but anyway:

                Why should using MSMQ require much maintenance ?

                Arne

                Comment

                • Andrew Ducker

                  #9
                  Re: Allowing applications to &quot;listen in&quot; to my app

                  On 5 May, 15:26, parez <psaw...@gmail. comwrote:
                  your main app writes to a msmq queue.
                  other applications : poll and peek the queue with cursor.
                  That would be possible - but I'd have to get MSMQ installed on a load
                  of boxes, so sadly that's out of the question.

                  Oh well.

                  Thanks anyway!

                  Andy

                  Comment

                  • parez

                    #10
                    Re: Allowing applications to &quot;listen in&quot; to my app

                    On May 6, 8:06 am, Andrew Ducker <and...@ducker. org.ukwrote:
                    On 5 May, 15:26, parez <psaw...@gmail. comwrote:
                    >
                    your main app writes to a msmq queue.
                    other applications : poll and peek the queue with cursor.
                    >
                    That would be possible - but I'd have to get MSMQ installed on a load
                    of boxes, so sadly that's out of the question.
                    >
                    Oh well.
                    >
                    Thanks anyway!
                    >
                    Andy
                    you dont have to install MSMQ on all the boxes.. unless its really
                    needed for your application.
                    You can one MSMQ installation and queue.(best case for number of
                    installtions)

                    if you have a load balanced environment then things will change..

                    Comment

                    • Marcin Hoppe

                      #11
                      Re: Allowing applications to &quot;listen in&quot; to my app

                      Arne Vajhøj pisze:
                      Why should using MSMQ require much maintenance ?
                      We used MSMQ for one of our projects and the server that hosted queues
                      was one big single point of failure :). I remember that those queues got
                      corrupted from time to time and required human intervention.

                      I don't have any experience neither with ActiveMQ nor MQSeries, but they
                      are likely more stable and scalable.

                      --
                      Marcin Hoppe
                      Email: marcin.hoppe@gm ail.com
                      Blog: http://devlicio.us/blogs/marcin_hoppe

                      Comment

                      Working...