I need to implement some form of communication mechanism in my application, to send notifications/messages from one application instance to all the others. This is a normal scenario where someone adds and item or deletes and item and you want to notify other users that this has happened.
The application runs on the client and connects to a database on the local network. So its not like all clients access a server instance of the application. So from what I know I could use MessageQueues or some form of Database polling where I have a table that stores all the messages (not ideal).
Issue is I need to implement this very quickly, so sadly can't go very complex but need the quickest easiest solution.
thanks for the help!
Sounds like it might be easier for you to use optimistic concurrency. Assume that things wont be deleted and deal with it at the affected client when it happens, which should be easier than developing some kind of concurrent notification system that won't scale at all...
Other than that, if you client list is small, db polling is the easiest way to do it without adding another layer of communication to your system, just add a table and implement a class library for everyone to do their thing on, if you can access the DB you are able to find out about deleted items etc.
Rhino Queues should do the trick. Its a super-lightweight queue which doesn't need MSMQ and is XCOPY deployable
http://ayende.com/Blog/archive/2009/04/03/rhino-queues-take-6.aspx
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With