In terms of diversity in operating systems, environments, and platforms, with limited host infrastructure resources to hold all systems the need arises design applications that run many or we can say platforms. This paper deals designing implementing a lightweight multithreaded client-server application appears as separate Docker container. Both client server containers are based on alpine Linu...

The paper studies a closed queueing network containing two types of node. The first type (server station) is an infinite server queueing system, and the second type (client station) is a single server queueing system with autonomous service, i.e. every client station serves customers (units) only at random instants generated by strictly stationary and ergodic sequence of random variables. It is...

Not long ago, industry-standard testing practices, which had evolved in response to quality issues facing the client/server architecture, centered either on the client for frontend functional tests, or the server for back-end scalability and performance tests. This "division of labor" derived largely from the fact that the classic client/server architecture, a two-tier structure, is relatively ...

Large client-server data intensive applications can place high demands on system and network resources. This is especially true when the connection between the client and server spans a wide-area internet link. In this paper, we consider changing the typical client-server architecture of a class of data intensive applications. We show that given sufficient common interest among multiple clients...

Existing techniques for a server to verify the correctness of client behavior in a distributed application suffer from imprecision, increased bandwidth consumption, or significant computational expense. We present a novel method for a server to efficiently search for a code path through the client that “explains” each client message, even though the server does not know local inputs to the clie...

The idea behind IDIPS is to provide ordered paths according to pre-defined criteria. IDIPS is composed of three entities: the client, the destination and the IDIPS server itself. The client is the entity sending request for QoS and path information towards a destination. The IDIPS server aims at providing the requested information to the client. IDIPS is operated by an ISP or an AS. A client se...

In a client-server system, when LRU or its variant buffer replacement strategy is used on both the client and the server, the cache performance on the server side is very poor mainly because of pages duplicated in both systems. This paper introduces a server buffer replacement strategy which uses a replaced page-id than a request page-id, for the primary information for its operations. The impo...

This article puts forth a networking paradigm, referred to as just-in-time (JIT) communication, support client-server applications with stringent request-response latency requirement. Of interest is not just the round-trip delay of network, but actual experienced by application. The JIT framework contains two salient features. At client side, communication layer will “pull” request from when th...

Client server application architecture is widely used in design and development of distributed application. Its advantage is the protocol design simplicity. However the architecture has several drawbacks such as server bottleneck and weak scalability. P2P architecture resolves these drawbacks by distributing computing tasks on both the client and server, making them equal in the system. However...