Assignment schemes for replicated services in Jini

Abstract

Abstract

Dreamer: A resource management architecture for Jini federation

“…In the worst case, clients may need to download all the replicated services and negotiate with these services one by one. In addition, lookup service has no capability to schedule client requests when all services are in use [4]. This is because lookup service does not know which service is overloaded or under loaded.…”

“…Georgiev and Getov [4] introduce and compare different schemes for assignments of replicated services in Jini. This paper divides the information scale of a Jini lookup service into four levels.…”

“…In addition, the searching process should not be complicated otherwise it would be time-consuming for the client to check all the services before finding a suitable one. It is expected that a client can subscribe to service if there is no available service currently [4]. Besides, when several clients attempt to get the same service, we need a method to decide client's priority.…”

“…Also, providing a way to determine and modify client's basic priority at runtime. (3) Enhancing Jini lookup service in knowing the service load status and adopting delayed assignment schemes [4] that always assign under loaded service to clients. This also facilitates the load balance in federation.…”

Dynamic Load-Balancing of Jini and .NET Services

“…Since the prototype implementations of Jini and .NET do not provide any loadbalancing mechanism [15,17], programmers have to explicitly incorporate code in clients to communicate with loadbalancing systems. Couples of load-balancing systems have been proposed and analyzed, and clients in these systems make requests to the load-balancing systems [4,5,7]. In other words, the process of load balancing is not transparent to clients.…”