SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

RMI Observing the Distributed Pattern .

isi avatar
isi
89 diapositives · 1K Views · Aug 08, 2014

Explore Remote Method Invocation (RMI) in Java with Adrian German, a Computer Science lecturer at Indiana University Bloomington. This session delves into how distributed computing operates, showcasing essential concepts, server-client relationships, and practical implementations. Through detailed code examples, learn the ways to broadcast messages, register clients, and manage distributed function calls. Understand key differences between local and distributed systems including latency, memory access, and concurrency issues. Join us to uncover the principles that underpin modern distributed applications.

#rmi observing the distributed pattern . #rmi observing the distributed pattern . ppt #powerpoint #presentation
RMI Observing the Distributed Pattern . - slide 1
01 / 89RMI Observing the Distributed Pattern .
1 / 17

Télécharger la présentation

RMI Observing the Distributed Pattern .
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. RMI Observing the Distributed Pattern. Adrian German Lecturer, Computer Science Indiana University Bloomington

  2. RMI Observing the Distributed Pattern. Java Adrian German Lecturer, Computer Science Indiana University Bloomington

  3. join

  4. registered

  5. join

  6. registered

  7. join

  8. registered

  9. broadcast

  10. broadcast “Hello!”

  11. broadcast( ) “Hello!”

  12. broadcast( ) “Hello!”

  13. “Hello!” “Hello!” “Hello!”

  14. client

  15. client client

  16. client client client

  17. client client server client

  18. client client server (host) client

  19. client client server (host) client The difference is that the server is listed in the phone book.

  20. client client server (host) client The difference is that the server is listed in the phone book (while a client isn’t).

  21. client client server (host) client How do we implement this?

  22. client client server (host) client

  23. client server (host)

  24. client server (host) class Server { Client[] clients; void broadcast(String message) { ... } int register(Client client) { ... } }

  25. client server (host) class Server { Client[] clients; void broadcast(String message) { ... } int register(Client client) { ... } } class Client { void register(int index, Client client) { ... } void update(Message msg) { ... } }

  26. client server (host) class Server { Client[] clients; void broadcast(String message) { ... } int register(Client client) { ... } } class Client { void register(int index, Client client) { ... } void update(Message msg) { ... } } Clients call the server's broadcast method in turn, which calls the clients' update.

  27. client server (host)

  28. server client

  29. server client

  30. server client f

  31. server client f f client.f(...) callsserver.f(...)

  32. server client g f f client.f(...) callsserver.f(...) which in turn calls client.g(...)

  33. server client g f f client.f(...) callsserver.f(...) which in turn calls client.g(...) The question is: how do we turn this code into a distributed program?

  34. server client g f f client.f(...) callsserver.f(...) which in turn calls client.g(...) The question is: how do we turn this code into a distributed program?

  35. (Hawaii) server Internet client (Sweden) g f f Internet client.f(...) callsserver.f(...) which in turn calls client.g(...) this local program The question is: how do we turn this code into a distributed program?

  36. even simpler

  37. server client value returned fun() add() function call

  38. server client value returned fun() add() class LocalProgram { public static void main(String[] args) { Server a = new Server(); Client b = new Client(); b.fun(a); } } function call class Server { int add(int a, int b) { return a + b; } } class Client { void fun(Server server) { System.out.println(server.add(1, 2)); } }

  39. server client value returned fun() add() class LocalProgram { public static void main(String[] args) { Server a = new Server(); Client b = new Client(); b.fun(a); } } function call • Important questions: • who creates the server? • who creates the client? • does the client really initiate anything?

  40. server client value returned fun() add() function call The difference between local and distributed computing is real. Differences are impossible to ignore at least in the following areas: a) latency, b) memory access, c) partial failure, and d) concurrency. ... that is, at least at the present time as well as in the near future.

  41. server client value returned fun() add() function call abstract class NetworkPeer implements java.rmi.Remote { public void exportMethods() throws java.rmi.RemoteException { java.rmi.server.UnicastRemoteObject.exportObject(this); } public java.rmi.Remote locatePeer(String peerHost, int peerPort, String peerName) throws Exception { return java.rmi.Naming.lookup("rmi://" + peerHost + ":" + peerPort + "/" + peerName); } public void startAsNetworkClient(String peerHost, int peerPort, String peerName) throws Exception { this.exportMethods(); java.rmi.Remote peer = this.locatePeer(peerHost, peerPort, peerName); this.startAsClientOf(peer); // see below ... } public abstract void startAsClientOf(java.rmi.Remote peer) throws java.rmi.RemoteException; public abstract void startAsServer(); // ... start as local server }

  42. server client value returned fun() add() function call abstract class NetworkPeer implements java.rmi.Remote { public void exportMethods() throws java.rmi.RemoteException { java.rmi.server.UnicastRemoteObject.exportObject(this); } public java.rmi.Remote locatePeer(String peerHost, int peerPort, String peerName) throws Exception { return java.rmi.Naming.lookup("rmi://" + peerHost + ":" + peerPort + "/" + peerName); } public void startAsNetworkClient(String peerHost, int peerPort, String peerName) throws Exception { this.exportMethods(); java.rmi.Remote peer = this.locatePeer(peerHost, peerPort, peerName); this.startAsClientOf(peer); // see below ... } public abstract void startAsClientOf(java.rmi.Remote peer) throws java.rmi.RemoteException; public abstract void startAsServer(); // ... start as local server } Distributed processing is a world of free agents. The class above is all that an object needs to become a free agent. Any object.