Do clients need a priori knowledge to use a service?
To use a service, clients will in general have a priori knowledge of at least one “known” (or “well-known”) Java interface that the service object implements. In other words, if a client program makes use of, say, a Jini storage service, the programmer of the client will usually know about a standard (or, “well-known”) interface to storage services when the programmer writes the client program.
Ans : To use a service, clients will in general have a priori knowledge of at least one “known” (or “well-known”) Java interface that the service object implements. In other words, if a client program makes use of, say, a Jini storage service, the programmer of the client will usually know about a standard (or, “well-known”) interface to storage services when the programmer writes the client program. Clients will usually specify one or more Java interfaces as part of the search criteria when looking for services on a lookup service. This approach means that clients will definitely know how to use the services they find, because by definition they know (have a priori knowledge of) at least one Java interface through which they can interact with the service. Currently, no “well-known” interfaces really exist. These interfaces will likely be defined by industry consortiums. For example, various manufacturers of printers have gotten together to define a hierarchy of interfaces for printing
To use a service, clients will in general have a priori knowledge of at least one “known” (or “well-known”) Java interface that the service object implements. In other words, if a client program makes use of, say, a Jini storage service, the programmer of the client will usually know about a standard (or, “well-known”) interface to storage services when the programmer writes the client program. Clients will usually specify one or more Java interfaces as part of the search criteria when looking for services on a lookup service. This approach means that clients will definitely know how to use the services they find, because by definition they know (have a priori knowledge of) at least one Java interface through which they can interact with the service. Currently, no “well-known” interfaces really exist. These interfaces will likely be defined by industry consortiums. For example, various manufacturers of printers have gotten together to define a hierarchy of interfaces for printing. As f
