What you are sayng i am only that want
Stephen is talking about the publisher/subscriber design
pattern. In a nutshell, each client application registers with the server that it wants to know about whatever changes.
Suppose your application displays weather, stock reports and news headlines (and say 30 other things). The user can configure it to only display certain parts. The client application would tell the server "I care about weather and stock reports". So, the server would only send that client weather and stock updates, but not news headlines.
Alternatively, you could write is so that your client asks the server for the weather and stock updates every 30 seconds, but not the stock reports (assuming that is how the user has it configured).