Listening to events published by other apps?

[wobbles]

Hi Everybody,

How do I go about listening to events published by other apps?
I know that my events are working internally (ie within my client),
but when I subscribe to an event published by a different client, it
doesn't work.

I feel like I'm missing something. Please point me in the right
direction.

Thanks in advance!

[Miha Markic]

Hi,

You should really take a look at remoting or message queue management.

--
Miha Markic - RightHand .NET consulting & development
miha at rthand com

<wobbles> wrote in message
news:ms********************************@4ax.com...

Hi Everybody,

How do I go about listening to events published by other apps?
I know that my events are working internally (ie within my client),
but when I subscribe to an event published by a different client, it
doesn't work.

I feel like I'm missing something. Please point me in the right
direction.

Thanks in advance!

[wobbles]

Hello Miha,

I was hoping you wouldn't say something like that.
That sounds pretty complicated.

Do you know of any online resources that explain what I should do?
If you could recommend a good book, that would be great too!

Thanks again

Hi,

You should really take a look at remoting or message queue management.

[Miha Markic]

You might take a look at .net help (very usefull) plus there are really nice
examples in .net sdk folder (
C:\Program Files\Microsoft Visual Studio .NET
2003\SDK\v1.1\Samples\Technologies\Remoting).

For message queues there is .net help topic
Message Queues and Messaging Technology Backgrounder
and others
--
Miha Markic - RightHand .NET consulting & development
miha at rthand com

"wobbles" <no***************************@killspam.hotmail.co m> wrote in
message news:8a********************************@4ax.com...

Hello Miha,

I was hoping you wouldn't say something like that.
That sounds pretty complicated.

Do you know of any online resources that explain what I should do?
If you could recommend a good book, that would be great too!

Thanks again

Hi,

You should really take a look at remoting or message queue management.

[wobbles]

Thanks Miha,

It's back to the books I go.
I don't always find the Microsoft help very easy to understand but
I'll give it a go.

Remoting/message queuing sounds quite complicated. Is it?

Thanks again.

On Thu, 11 Dec 2003 21:28:48 +0100, "Miha Markic" <miha at rthand com>
wrote:

You might take a look at .net help (very usefull) plus there are really nice
examples in .net sdk folder (
C:\Program Files\Microsoft Visual Studio .NET
2003\SDK\v1.1\Samples\Technologies\Remoting).

For message queues there is .net help topic
Message Queues and Messaging Technology Backgrounder
and others

[Miha Markic]

Hi wobbles,

Actually it is pretty simple.
Check out the samples (for remoting).

--
Miha Markic - RightHand .NET consulting & development
miha at rthand com

"wobbles" <no***************************@killspam.hotmail.co m> wrote in
message news:nn********************************@4ax.com...

Thanks Miha,

It's back to the books I go.
I don't always find the Microsoft help very easy to understand but
I'll give it a go.

Remoting/message queuing sounds quite complicated. Is it?

Thanks again.

On Thu, 11 Dec 2003 21:28:48 +0100, "Miha Markic" <miha at rthand com>
wrote:

You might take a look at .net help (very usefull) plus there are really niceexamples in .net sdk folder (
C:\Program Files\Microsoft Visual Studio .NET
2003\SDK\v1.1\Samples\Technologies\Remoting).

For message queues there is .net help topic
Message Queues and Messaging Technology Backgrounder
and others

[Dmitriy Lapshin [C# / .NET MVP]]

Miha, Wobbles,

* Remoted events have a very unpleasant feature - the order in which event
handlers will be called is unpredictable as remoting requests are served on
the thread pool. If the event order is not important, you can probably
ignore that warning. But if it IS important, remoting seems to be useless.

* Message Queues require MSMQ to be installed, don't they?

* I have used Named Pipes for delivering events across process boundaries
and they work just fine. The only caveat is that you should resort to
P/Invoke to create and initalize both ends of the pipe. Then, the FileStream
class constructed from the pipe handle works with the pipe almost as it was
a regular file.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

"Miha Markic" <miha at rthand com> wrote in message
news:Ox**************@tk2msftngp13.phx.gbl...

Hi wobbles,

Actually it is pretty simple.
Check out the samples (for remoting).

--
Miha Markic - RightHand .NET consulting & development
miha at rthand com

"wobbles" <no***************************@killspam.hotmail.co m> wrote in
message news:nn********************************@4ax.com...

Thanks Miha,

It's back to the books I go.
I don't always find the Microsoft help very easy to understand but
I'll give it a go.

Remoting/message queuing sounds quite complicated. Is it?

Thanks again.

On Thu, 11 Dec 2003 21:28:48 +0100, "Miha Markic" <miha at rthand com>
wrote:

You might take a look at .net help (very usefull) plus there are really niceexamples in .net sdk folder (
C:\Program Files\Microsoft Visual Studio .NET
2003\SDK\v1.1\Samples\Technologies\Remoting).

For message queues there is .net help topic
Message Queues and Messaging Technology Backgrounder
and others

[Miha Markic]

> * Remoted events have a very unpleasant feature - the order in which event

handlers will be called is unpredictable as remoting requests are served on the thread pool. If the event order is not important, you can probably
ignore that warning. But if it IS important, remoting seems to be useless.
Yup.
* Message Queues require MSMQ to be installed, don't they - they are free though?

Don't forget disconnected feature.
* I have used Named Pipes for delivering events across process boundaries
and they work just fine. The only caveat is that you should resort to
P/Invoke to create and initalize both ends of the pipe. Then, the FileStream class constructed from the pipe handle works with the pipe almost as it was a regular file.

Right. Though you can't use them outside intranet as is the case with MSMQ.

--
Miha Markic - RightHand .NET consulting & development
miha at rthand com

[wobbles]

Miha, Dimitriy,

Thanks for your input.
I'll have a look at remoting as well as MSMQ and "named pipes".

wobbles
On Fri, 12 Dec 2003 19:02:11 +0100, "Miha Markic" <miha at rthand com>
wrote:

* Remoted events have a very unpleasant feature - the order in which event
handlers will be called is unpredictable as remoting requests are served

on

the thread pool. If the event order is not important, you can probably
ignore that warning. But if it IS important, remoting seems to be useless.

Yup.

* Message Queues require MSMQ to be installed, don't they - they are free

though?

Don't forget disconnected feature.

* I have used Named Pipes for delivering events across process boundaries
and they work just fine. The only caveat is that you should resort to
P/Invoke to create and initalize both ends of the pipe. Then, the

FileStream

class constructed from the pipe handle works with the pipe almost as it

was

a regular file.

Right. Though you can't use them outside intranet as is the case with MSMQ.