Allowing applications to "listen in" to my app

[Andrew Ducker]

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]

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

 

[Marcin Hoppe]

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!

 

[parez]

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.

 

[Marcin Hoppe]

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.

 

[parez]

parez pisze:


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

 

[Arne Vajhøj]

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

 

[Arne Vajhøj]

parez pisze:

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

 

[Andrew Ducker]

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

 

[parez]

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

 

[Marcin Hoppe]

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.