Chapter 12-3


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Chapter 12-3

  1. 1. Network Services M. L. Liu
  2. 2. Sources of Information <ul><li>Jini(tm ) Network Technology , http:// / </li></ul><ul><li>Core Jini, a book by Keith Edwards </li></ul><ul><li>Jan Newmarch's Guide to JINI Technologies , </li></ul><ul><li>Jini Planet , </li></ul><ul><li>Directory of Jini ™ Resources on the net: Tutorials_and_Examples , </li></ul>
  3. 3. Sources of Information <ul><li>Jini whitepaper , </li></ul><ul><li>California Software Lab | Jini by Example – Whitepaper , </li></ul><ul><li>Noel Enete’s Nuggets for Jini (code samples), </li></ul><ul><li> -- The Community Resource for Jini(tm ) Technology , </li></ul>
  4. 4. Distributed Application Paradigms
  5. 5. Network Services <ul><li>The network is seen as federations of services and clients. </li></ul><ul><li>Services can be located through a directory service. </li></ul><ul><li>Services can be discovered using a lookup service and a discovery protocol. </li></ul><ul><li>Services can join the community and register its availability with one or more lookup services. </li></ul>
  6. 6. Network Services <ul><li>The network is seen as federations of services and clients . </li></ul><ul><li>Services include applications, databases, servers, devices, information systems, mobile appliances, storage, printers, and clients are requesters (and consumers) of services </li></ul>
  7. 7. Network Services <ul><li>Each federation of client and service(s): </li></ul><ul><ul><li>is independent of other federations and may co-exist with other federations. </li></ul></ul><ul><ul><li>is transient: the union lasts only for as long as the service(s) is/are needed. </li></ul></ul><ul><li>There is no centralized control system: </li></ul><ul><ul><li>There is no centralized administration of available services </li></ul></ul><ul><ul><li>There are no policies that restrict federation between client and services. </li></ul></ul>
  8. 8. Java’s Jini Technologies <ul><li>Jini provides an infrastructure and a programming model based on federation of network services. </li></ul><ul><li>It uses RMI to transport objects </li></ul><ul><li>It allows a client program to make use of services without being aware of the “wire protocol” used by the service. </li></ul><ul><li>It provides the concept of leasing a service: a client requests the lease of a service, which expires after a time period. </li></ul>
  9. 9. Jini <ul><li>A service is an object that implements a service API. </li></ul><ul><li>A client looks up a service that supports an API. </li></ul><ul><li>A discovered service object is sent to the client. </li></ul><ul><li>The client and the service only have to agree on the API, and not how requests and responses are transmitted. </li></ul>
  10. 10. Jini <ul><li>Jini is to network services what universal plug-and-play is to system devices: it allows interoperability of clients and services regardless of transport and “wire” protocols. </li></ul>
  11. 11. Figure from “Jini By Example”
  12. 12. Jini code samples: <ul><li>HelloWorld – </li></ul><ul><ul><li>“ nugget” JiniExample1 illustrates network service lookup </li></ul></ul><ul><ul><li>“ nugget” JiniExample3 illustrates network service discovery </li></ul></ul><ul><li>( Noel Enete’s Nuggets for Jini (code samples), </li></ul><ul><li>Calculator </li></ul><ul><ul><li>See “jini by Example” paper from California Software Lab. </li></ul></ul><ul><li>California Software Lab | Jini by Example – Whitepaper , http:// </li></ul>
  13. 13. Applications <ul><li>Shared network devices </li></ul><ul><li>Service (software, video, music, etc.) on demand </li></ul><ul><li>Shareware </li></ul>