Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Jini Network Technology

on

  • 1,798 views

Jini Network Technology

Jini Network Technology

Statistics

Views

Total Views
1,798
Views on SlideShare
1,750
Embed Views
48

Actions

Likes
1
Downloads
77
Comments
0

1 Embed 48

http://kwangshin.pe.kr 48

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 종종 발표자는 주제나 어휘에 익숙하지 않은 청중에게 기술적 성격의 자료를 전달해야 합니다 . 자료는 복잡하거나 많은 양의 상세 정보를 나타낼 수 있습니다 . 기술적인 자료를 효과적으로 발표하려면 Dale Carnegie Training® 의 지침 따라 하기를 이용하십시오 . 사용 가능한 시간의 양을 고려하여 자료를 구성하도록 준비하십시오 . 주제의 범위를 좁히십시오 . 프레젠테이션을 명확하게 부분으로 나누십시오 . 논리적으로 진행하십시오 . 처음부터 끝까지 요점을 유지하십시오 . 요약 , 주요 단계의 반복 , 논리적 결론으로 프레젠테이션을 끝맺음 하십시오 . 청중이 시종일관 집중할 수 있도록 하십시오 . 예를 들어 , 반드시 데이터는 명확하고 정보는 관련이 있도록 하십시오 . 상세 정보와 어휘의 수준이 청중에 적합하도록 유지하십시오 . 주요 요점과 단계를 뒷받침 하기 위해 시각적 요소를 사용하십시오 . 청중의 욕구에 주의를 기울이십시오 . 그러면 청중이 이해하는 데 도움이 될 것입니다 .
  • 소개에서 청중과 주제의 관련성을 전달하십시오 . 프레젠테이션의 간략한 시연을 제공하고 이 프레젠테이션이 청중에게 얼마나 중요한지를 입증하십시오 . 어휘 , 예제 , 설명을 선택할 때는 청중의 관심사와 전문가적 지식 수준을 고려하십시오 . 주제가 청중에게 중요하다는 점을 강조하면 청중의 주의를 끄는 데 도움을 줍니다 .

Jini Network Technology Jini Network Technology Presentation Transcript

  • J ini TM N etwork T echnology 2001. 2. 17. Kwang Shin Oh Dept. of Research & Development http://raytrust.pe.kr [email_address] kr Copyright 2001 © Kwang Shin Oh
  • Agenda
    • Why Jini TM ?
    • What is Jini TM ?
    • Jini TM Architecture Overview
    • The Details
    • Example Service Model
    • Jini TM Roadmap
    • Reference
  • Why Jini TM ?
    • Distributed computing is more difficult than local computing because of :
      • Network latency
      • Concurrency issues
      • Memory management
      • Inevitable partial failure
  • Evolution of distributed computing
    • Key insight : Remote increasingly looks local
  • What is Jini TM ?
    • Jini addresses the problems of distributed computing using a set of simple interfaces and protocols
    • Jini enables spontaneous network of software services(and devices) to assemble into working groups of objects, or Federations
    • Jini builds on the Java TM 2 Platform
  • What is Jini TM ?
    • Jini enables self-healing when one or more devices are removed from the Federation
    • Jini is usable for hardware as well as software services
      • Everything is represented by Java Objects
      • Everything is located and accessed through Java Interfaces
  • Jini TM Architecture Overview
  • Java Technology Features that Benefit Jini TM
    • Feature Benefit
    • Java Virtual Machine  Homogeneous network
    • Portable object code  Architecture independence
    • Downloadable code  Dynamic environment
    • Unified type system  No impedance mismatch
  • Jini TM Extends the Java Platform
    • The Details :
    • Jini Infrastructure
  • Jini TM Lookup Service
    • Repository of available services
    • Stores each service as Java objects
    • Clients download services on demand
  • Lookup service
    • May be federated with other lookup services
    • Lookup service interface provides:
      • Registration
      • Access
      • Search
      • Removal
  • Discovery and Join Protocols
    • Used to find and join a group of services
    • Based on UDP multicast
    • Services advertise capabilities
    • Provide required software drivers
    • Establish reference with lookup service
    • Unicast discovery also supported
  • Discovery Protocol
  • Discovery Protocol – 1
    • The Multicast Request Protocol
      • allows an entity that has just been started to actively discover nearby lookup services
    multicast request multicast response unicast request unicast response Join Protocol Discovering Entity Lookup Service
  • Discovery Protocol – 2
    • The Multicast Announcement Protocol
      • allows lookup services to announce their availability within multicast radius
    multicast announce unicast request unicast response Join Protocol Discovering Entity Lookup Service
  • Discovery Protocol – 3
    • The Unicast Discovery Protocol
      • allows an entity that has just been started to directly discover known lookup service
    unicast request unicast response Join Protocol Discovering Entity Lookup Service
  • Join Protocol
  • Join Protocol
    • The Join Protocol
    service registration new lease Discovery Protocol lease renew lease renewal lease expire Joining Entity Lookup Service
  • Steps in Discovery and Join
    • Jini TM enabled Object(representing a hardware and/or software service) multicasts a packet with a reference to itself
    • The service receives RMI reference to Lookup service(one or more)
    • The Service joins a Federation by placing an object representing its capabilities into the Lookup service for other clients and services to use
  • Traditional Technology
    • Device is added to computer
    • Device definition is edited in node configuration table
    • Computer is restarted
    • Updated configuration table is pushed to network device map
  • Jini Technology
    • Device is plugged in and powered up
      • Lookup service receives multicast
      • Lookup service authenticates source
      • Lookup service sends advertisement
      • Device joins Lookup service
  • Finding a Service
    • To find a service, a Jini client locates service by querying a Lookup Service by type(Java Interface)
    • Code moves from service to client via Lookup Service
    • Code needed to use service is dynamically loaded on demand
  • Finding a Service
  • Using a Service
    • Communication is between service and its proxy
    • Independent of wire protocol
    • Protocol can change without affecting client
    • RMI semantics core to functionality
  • Using a Service
  • Why Jini TM uses RMI
    • RMI can pass entire Java objects and their code
    • Works in any compliant JVM
    • Provides automatic serialization, transport, and de-serialization of objects
    • Robust and configurable security options(RMI over SSL, Authenticated Principal, etc.)
    • The Details :
    • Jini Services
  • Services
    • Represented by Java Interfaces
      • Separation of “how” from “what”
      • Implement in hardware or software
      • Implementations can change over time
      • Multiple implementations
  • Services Enable Evolution
    • Base interfaces can be extended to :
      • Add new functionality
      • Combine functionality
    • Old clients can use base interface
    • New clients can use extended interface
    • Allows evolution of implementation without changing clients or infrastructure
  • Services Are Defined by Java Interfaces
  • Services Are Defined by Java Interfaces
  • Client Finds Service by Interface
  • Client Finds Service by Interface
  • Client Finds Service by Interface
  • Service Interfaces
    • Community driven
      • Printing
      • Service UI
    • Don’t have to be done by Sun
    • Only base types need to be common
    • Interfaces can evolve
      • New apps can use new functionalities
      • Old apps still work
  • Legacy Services
    • Jini requires Java at the network
      • Services identified by Java type
      • Proxies may need code downloaded
    • Implementation can be non-Java
      • Wrap legacy language in Java
      • make calls to legacy with JNI
    • The Details :
    • Example Service Models
  • Example service model #1: Local device concentrator
  • Example service model #2: Remote device concentrator
  • Example service model #3: EJB services
  • Detailed Example: Jini-Enabled Printer
  • Discovery
    • Multicast query for lookup service
  • Discovery
    • Lookup service discovered
  • Join
    • Printer registers service object with LUS
  • Locating Service
    • Client asks LUS for Printer
  • Locating Service
    • LUS returns printer service object to client
  • Using the Service
    • Client communicates to printer through service object
  • Jini TM Roadmap
    • Jini TM Technology Starter Kit
      • Version 1.0  Jan, 1999
      • Version 1.0.1  Nov, 1999
      • Version 1.1Alpha  Nov, 1999
      • Version 1.1Beta  May, 2000
      • Version 1.1  Oct, 2000
  • Reference
    • Jini TM Connection Technology Architecture Overview
      • Bill Day – Sun Microsystems
    • Jini TM Technology Core Platform Specification Version 1.1
      • October 2000 Sun Microsystems
    • Core JINI – W.Keith Edwards
      • 1999 Prentice Hall