
<script type="text/javascript">
<!--
document.write('<div id="oa_widget"></div>');
document.write('<script type="text/javascript" src="https://www.openaire.eu/index.php?option=com_openaire&view=widget&format=raw&projectId=undefined&type=result"></script>');
-->
</script>The amount of data sent in the network conspicuously affects the network performance and it also adds significant latency to the applications. Various data compression techniques have been in use for decades providing both storage efficiency as well as transmission efficiency. For applications that communicate over a network with limited bandwidth, efficient bandwidth utilization not only depends on the amount of data sent in the network, but also on the number of calls made between the applications, especially in client–server models. Therefore something apart from the techniques of data compression has to be ordained to achieve the latter. Mitigating the number of calls made between the client and the server should not affect the data consistency between them, thereby making the applications unreliable. I propose a model to be incorporated in the client–server frameworks to achieve efficient bandwidth utilization, by constricting the number of calls made between the two applications, and also the amount of data sent. Since there is a considerable amount of information sent on each call, reduction in the number of calls results in a substantial reduction in data transmissions. The information sent on each call, not only refer to the TCP/IP setup, but also the server’s original response to a request from another client. I confer the “eBUCS” protocol, which will be intricately tied up with the client–server frameworks, and also the scenarios under which the protocol will limit itself in order to avoid its adverse effects on the latency.
| citations This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 1 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average | 
