They best bet would be to create this application as a Windows Service considering all the client applications will reside on the same PC.
One of the other challanges you will have to tackle is that one of your client is in Java. If all the clients were in .NET then you could create a .NET Remoting based application that can take care of acting as a broker app. But .NET Remoting does not talk to Java.
You you might end up using Sockets to communicate with the client applications. As soon as a Broker request comes in, the Broker can then broadcast the message to other intrested applications listning for new messages.
--
Regards,
Saurabh Nandu
AksTech Solutions, reflecting your needs...
[
www.AksTech.com ]
[
www.MasterCSharp.com ]
"Tom Q" wrote:
> A user has multiple applications running on his/her PC and I want to create
> a broker component or service that is shared among the multiple apps. Each
> time an application changes a record it notifies the broker and the broker
> in turn notifies the other applications so they can take appropriate
> actions. Any one app may send a string data to the broker and the broker
> makes this string data available to all the other apps. This has to happen
> instantaneously.
>
> 1) I would prefer to use .NET C# to develop the broker component .
> 2) The broker component must be able to raise event (to notify) in any of
> the multiple applications (or use callback functions?)
> 3) The broker component also run on the user's PC and only one instance of
> it is shared by all applications.
> 4) One of the applications was written in Java.
>
> My question is what should this broker component be created as (project
> type)? A Windows service, a Serviced Component, Message Queue Component or
> just Class Library? Keeping in mind that some of the apps may not be able
> to work with the Message Queue component for example.
>
> Thanks
> Tom
>
>
>
Similar Threads
