G
Guest
Hi to all!
We are designing a dll that needs to send some information periodically to a
possible interface application that is listening to these messages.
The information, which consist on a complex structure with several fields,
must be sent periodically, and although the frequency depends on calculations
in the dll, on average we can say that a new message is being sent every 33
milliseconds.
Is very important to note that the dll must proceed with its work after
sending the message without waiting for the interface to finish reading the
new info. The dll does not care about the treatment that the interface is
doing and is not waiting for any results, so we can talk about an
asynchronous way of sending the information. Indeed, the dll doesn’t know
anything about the interface application, and it must be possible to develop
a new listener interface once the dll has been completely finished.
The dll is being developed in C++ using Microsoft Visual Studio .NET 2003
(.NET Framework 1.1) .
We would like to know what is the best way of achieving this communication:
what mechanism is the best one to use in the dll and how should an interface
listen to it.
If possible, we would like to know how to do it in two situations:
1. Supposing that any possible interface will be coded using .NET
environment (.NET Libraries, Managed code, etc…)
2. Thinking of a more general interface, that could be coded without using
..NET.
Thanks in advance!
We are designing a dll that needs to send some information periodically to a
possible interface application that is listening to these messages.
The information, which consist on a complex structure with several fields,
must be sent periodically, and although the frequency depends on calculations
in the dll, on average we can say that a new message is being sent every 33
milliseconds.
Is very important to note that the dll must proceed with its work after
sending the message without waiting for the interface to finish reading the
new info. The dll does not care about the treatment that the interface is
doing and is not waiting for any results, so we can talk about an
asynchronous way of sending the information. Indeed, the dll doesn’t know
anything about the interface application, and it must be possible to develop
a new listener interface once the dll has been completely finished.
The dll is being developed in C++ using Microsoft Visual Studio .NET 2003
(.NET Framework 1.1) .
We would like to know what is the best way of achieving this communication:
what mechanism is the best one to use in the dll and how should an interface
listen to it.
If possible, we would like to know how to do it in two situations:
1. Supposing that any possible interface will be coded using .NET
environment (.NET Libraries, Managed code, etc…)
2. Thinking of a more general interface, that could be coded without using
..NET.
Thanks in advance!