Would be a pretty good idea… At least, I can see some considerable value in it, but… Unfortunately, in general case, and, even more unfortunately, in most cases, this is impossible to have notifications on the client side. Why? In a few words:
domination of client-server model, lack of server push, lack of publisher-subscriber model.
For some background, please see:
http://en.wikipedia.org/wiki/Client-server_model[
^],
http://en.wikipedia.org/wiki/Polling_%28computer_science%29[
^],
http://en.wikipedia.org/wiki/Pull_technology[
^],
http://en.wikipedia.org/wiki/Server_push[
^],
http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern[
^].
Well, yes, on client side you still could resort to client
polling of all the services, but this approach, being popular enough, is so disgusting that I don't want to discuss it. I think this approach is clear enough, especially if you read the articles referenced above.
Some thoughts:
A while ago, even the client-server approach, especially in database management field, was perceived as revolutionary and progressive by many naive users and developers, if not the most of them. The effect of the contrast with the nightmare of before-networks and file system based products has played its role. Even though the draconian limitations of client-server/pull technology was quite apparent to those who could really think, as well as the absolute feasibility of more comprehensive technologies, not many listened to the voice of the reason. And now, such think where the lack of server push because nearly 100% apparent, because it hurts even the very basic needs, such as reasonably designed chat application, people come back to server push or publisher-subscriber, feeling much more resistance due to standards and technologies created by inertia of thinking (and even such things as firewalls). Any example of such workaround? This is a pretty striking one:
http://en.wikipedia.org/wiki/SignalR[
^],
http://www.asp.net/signalr[
^].
—SA
Submit an article or tip