| T. G. Lewis. "Where is client/server software headed?" IEEE Computer, pages 49--55, April 1995. |
....queueing network models to include contention effects for software resources such as server tasks, as well as contention for hardware devices. It is appropriate for assessing the performance of many kinds of distributed systems, including client server applications [1] peer to peer applications [32], communications switching software [4] transaction processing systems (e.g. ENCINA [24] and systems based on midware software technologies [5] such as CORBA [35] or DCE [13] TLC incorporates enough detail to construct an LQN model for these types of systems. TLC grew out of a technique ....
T. G. Lewis. "Where is client/server software headed?" IEEE Computer, pages 49--55, April 1995.
....the standard Jada distributed object model is based on Remote Method Invocation (RMI) an object oriented RPC mechanism. The simple client server relationship allowed by RMI is not flexible enough to express all the kinds of relationships a distributed system can activate among its components [Lewis 1995]. RMI allows remote applets to enact a client server relationship but things get more difficult when we have to program more complex cooperation protocols. If the WWW has to become an infrastructure for both developing and implementing business applications in distributed and collaborative ....
Lewis, T. (1995), "Where is Client/Server Software Headed?" IEEE Computer 28 , 4, 49--55.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC