DCOM people,
I used to use TIBCO Rendezvous software to do the following, but I
can't anymore, so I have implemented my solution using DCOM.
I have a DCOM server component that receives events from an external
data provider, writes this data to a SQL Server database and raises a
new data event.
This event is then received by several "listening" client components.
Depending on each client's preferences, this may or may not lead to
the querying of the database for the new information.
Sometimes (I'm guessing when a lot of data comes in from the external
source) there can be a delay as messages appear to be queueing up at
the server component. From what I understand of DCOM, processing
cannot continue on the server component until all the clients have
processed the event that was raised.
I would rather make the events asynchronous, and I understand you can
do that using threads but that sounds too difficult. Is there a
simple way to keep the clients up to date with new data developments,
without them being "connected" to the server component?
Hope someone can help me here.
Many thanks,
- Mike Carter