How to harden BS into CS? What technologies are required? Is there a ready-made framework? There are two main purposes for doing so:
1. Save traffic.
Transmit as little data as possible between the browser and the server.
2. saving server resources.
The operations that can be performed in the browser should be stored in the browser as much as possible.
I heard that the domestic site construction cost is much higher than the international site construction cost. After a rough look, it seems to be much higher than that in other countries, and the most surprising thing is that the billable space actually has limited traffic. When I use a foreign space, I only find that the free space is limited, and the traffic is never Limited.
I feel that the following technical problems should be solved:
1. server push
HTML5 perfectly supports server push, so my idea is to seduce users to install browsers that support HTML5. This article introduces many server push methods:
Http://www.cnblogs.com/moxiaoyu/archive/2012/03/06/comet_java_ajax.html
2. Multicast
This is definitely an artifact that can save the bandwidth to the extreme. And it seems that it can be implemented. baidu search "multicast WEB" can find some. But I don't know whether to install the plug-in. if you need to install the plug-in, the effect will be greatly reduced.
3. receive confirmation
It seems that you can confirm whether there are unreceived messages through continuous sequences. Similar to the TCP transmission protocol. In this way, you can avoid sending a message to the server to confirm that the message has been received. I wonder whether server push provided by HTML5 can provide the receiving and confirmation function without consuming server resources.
This is just a question that I think of. I hope you can help me come up with more questions.
The final part is the framework. Such a wonderful project will certainly consume a lot of manpower, but it will be much easier if there is a framework.
Reply to discussion (solution)
In the rich client environment, the only difference between B/S and C/S is that the former has no user interface overhead.
