Client Lookup

The client, on the other hand, is trying to get a copy of the service into its own JVM. It goes through the same mechanism to get a registrar from the lookup service. But this time it does something different, which is to request the service object to be copied across to it. This process is shown in Figures 1-7, 1-8, 1-9, and 1-10. Figure Overview of Jini.7, “Figure 1-7. Querying for a service locator”, Figure Overview of Jini.8, “Figure 1-8. Registrar returned”, Figure Overview of Jini.9, “Figure 1-9. Asking for a service”, and Figure Overview of Jini.10, “Figure 1-10. Service returned”.

Figure Overview of Jini.7. Figure 1-7. Querying for a service locator

Figure 1-7. Querying for a service locator

Figure Overview of Jini.8. Figure 1-8. Registrar returned

Figure 1-8. Registrar returned

Figure Overview of Jini.9. Figure 1-9. Asking for a service

Figure 1-9. Asking for a service

Figure Overview of Jini.10. Figure 1-10. Service returned

Figure 1-10. Service returned

At this point, the original service object is running on its host, there is a copy of the service object stored in the lookup service, and there is a copy of the service object running in the client's JVM. The client can make requests of the service object running in its own JVM.