The Accuracy of the Clock Synchronization Achieved by TEMPO in Berkeley UNIX 4.3BSD
IEEE Transactions on Software Engineering
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
The design and performance of a real-time CORBA event service
Proceedings of the 12th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
Pattern-Oriented Software Architecture: Patterns for Concurrent and Networked Objects
Pattern-Oriented Software Architecture: Patterns for Concurrent and Networked Objects
Scheduling and simulation: how to upgrade distributed systems
HOTOS'03 Proceedings of the 9th conference on Hot Topics in Operating Systems - Volume 9
Patterns for Fault Tolerant Software
Patterns for Fault Tolerant Software
Hi-index | 0.00 |
To create constantly evolving software, the upgrading is an essential factor. There are two ways to upgrade, pushing and polling. Polling has the advantage of keeping the latest versions of all the clients, but can cause heavy server load by simultaneously connections to many clients and unnecessary network traffics. On the other hand, push causes much less because push can upgrade the specific clients, but there is cumbersome monitoring to keep stopped clients on latest version. The Half-Push/Half-Polling pattern mixes these two different ways, keeping their advantages, eliminating their disadvantages.