Ok, around the server side there is a desktop application which is often used to place some good info right into a database (news,images,ect..) and that i have clients which gather these details from database and store them to their local XML .

So each client downloads news from database and shows them .

The problem is when I'm able to inform clients that there's an update .

My Solution

I figured utilizing a database filed like UpdateID ,as well as on each data update into database UpdateID ought to be Incremented +1, then every client must have a characteristic UpdateID to their XML, and appearance if their UpdateID matches the Server UpdateID, otherwise than this can be a new update. On each effective update, clients should place server UpdateID to their XML UpdateID .

Same with there much better way to accomplish this ?

PS : The Information Re-present layer which im using is really a WCF Service

I believe the pull model that you simply propose is most likely the simplest to implement and many straightforward means to fix the issue. Knowing that you're using WCF webservices, however, you will find the possible ways to implement a push model using WCF Callbacks. Within this model you are writing service contracts just like normal but here the clients register on their own the server. On data updates around the server the server calls a callback function on all registered clients, which respond by fetching new data.

The normal showcase application with this model is really a ticketing system, where tickets are reserved and launched frequently. This method removes the requirement for clients to constantly poll the server.

The content known as Eliminate Server Polling with WCF Callbacks gives more particulars about them as well as has a ticketing system example. This article also describes this process.

That does not mean this is preferable to that which you suggest yourself, however it might be worth considering.