Our desktop application require to be updated directly when a mobile employee sends any message from his/her windows phone 7 mobile.

Currently our requirement is that send a message from our desktop application to a Windows Phone 7.5 which we are able to achive easily using PUSH Notifications, Now when the user takes some action against the sent message the windows phone app calls the WCF service and pass the message to that WCF which receives the message and puts into the database and desktop application reads it later and this is where problem lies. Because our WCF is putting that message into database our application is polling it every 5 second and if any replies received from any of our drivers then it is updating the UI.

What we want to achieve is when we receive any reply our desktop applicaton should be notified automatically and udpates the UI and then put it into the database.

So please share your experience on this issue.

Isn't this what SQL Server Notifications Services, is all about?

Notification servies are gone and are no more in SQL server 2008 r2, as a substitute they have introduced SQL Server 2008 R2 ​Stream​Insight.

No idea what is this and how I am gonna utilize it in my application, not time to introduce new thing in the running close to deadline project.

Thanks

Isn't it basic inter-process communication? It's the same as with a chat client/server. You have a server to which the client has a network connection through a socket. (there are variants for this, even websockets, you can find more info about this through google and check what you need, e.g. named pipes might be easiest if you are on the same network). Your phone application calls a service, the service does the work and calls the server the client has connection to to send the clients a message that things have been updated. The client receives over its network connection the message from the server and refreshes.

There are various ways to perform interprocess communication, and you need 2-way communication, not call-respond, so essentially the same as a basic chat-client/server, which are in its simplest form build on sockets, but there are other ways.

You are correct Otis, thats what I am researching on at the moment it looks like to me the only possible way to my scenario