Remoting patterns

More documents

Recommendations

Info

Pattern: Invoker • Context: • A requestor sends a remote invocation for a remote object to a server • Problem: • Somehow the targeted remote object on the server has to be reached • Simplest solution: remote object is addressed over the network directly • Solution: • Large number of object → not enough network endpoints • Remote object would have to deal with network connections, receiving and demarshalling messages, etc. • Invoker(s) accept(s) invocations from requestors • Invoker reads the request and demarshalls it • Looks up the correct local object & operation and • Performs the invocation on the targeted remote object 26 Uwe Zdun, Markus Voelter, Michael Kircher - <strong>Remoting</strong> Patterns.
Pattern: Invoker (2) Process A2 Client Process A1 Client Requestor Client Proxy Machine Boundary Process B Invoker Invoker Remote Object Remote Object Remote Remote Object Remote Object Object Requestor 27 Uwe Zdun, Markus Voelter, Michael Kircher - <strong>Remoting</strong> Patterns.
Page 1 and 2: Remoting Patterns Uwe Zdun, Markus
Page 3 and 4: Patterns and Pattern Languages 3 Uw
Page 5 and 6: Elements of a Pattern • Name •
Page 7 and 8: From Patterns to Pattern Languages
Page 9 and 10: Distributed Systems: Application Ar
Page 11 and 12: Distributed Systems: Challenges •
Page 13 and 14: Remoting Styles • There are syste
Page 15 and 16: Remoting Patterns • Numerous proj
Page 17 and 18: Pattern: Broker (2) Process A Proce
Page 19 and 20: Server Application • Remote objec
Page 21 and 22: Basic Remoting Patterns INTERFACE D
Page 23 and 24: Pattern: Requestor (2) Process A Pr
Page 25: Pattern: Client Proxy (2) Process A
Page 29 and 30: Pattern: Server Request Handler (2)
Page 31 and 32: Pattern: Client Request Handler (2)
Page 33 and 34: Pattern: Marshaller (2) Client Proc
Page 35 and 36: Pattern: Interface Description (2)
Page 37 and 38: Pattern: Remoting Error (2) Process
Page 39 and 40: Interactions: Client-Side Invocatio
Page 41 and 42: Interactions: Remoting Error Propag
Page 43 and 44: Identification Patterns Client look
Page 45 and 46: Pattern: Object ID (2) Process A1 C
Page 47 and 48: Pattern: Absolute Object Reference
Page 49 and 50: Pattern: Lookup (2) Process C Proce
Page 51 and 52: Interactions: Marshalling of Absolu
Page 53 and 54: Lifecycle Management Patterns SERVE
Page 55 and 56: Pattern: Static Instance (2) Proces
Page 57 and 58: Pattern: Per-Request Instance (2) P
Page 59 and 60: Pattern: Client-Dependent Instance
Page 61 and 62: Pattern: Lazy Acquisition (2) Proce
Page 63 and 64: Pattern: Pooling (2) Process A Clie
Page 65 and 66: Pattern: Leasing (2) Process A Clie
Page 67 and 68: Pattern: Passivation (2) Process A
Page 69 and 70: Interactions: Per-Request Instance
Page 71 and 72: Interactions: Leased Creation Clien
Page 73 and 74: Interactions: Passivation Invoker i
Page 75 and 76: Extension Patterns Client CLIENT PR
Page 77 and 78:
Pattern: Invocation Interceptor (2)
Page 79 and 80:
Pattern: Invocation Context (2) Pro
Page 81 and 82:
Pattern: Protocol Plug-In (2) Proce
Page 83 and 84:
Interactions: Server-Side Security
Page 85 and 86:
optimizes resource consumption upda
Page 87 and 88:
Pattern: Lifecycle Manager (2) 2a)
Page 89 and 90:
Pattern: Configuration Group (2) Se
Page 91 and 92:
Pattern: Local Object (2) Server Pr
Page 93 and 94:
Pattern: QoS Observer (2) 1) Serve
Page 95 and 96:
Pattern: Location Forwarder (2) Pro
Page 97 and 98:
Invocation Asynchrony Patterns 97 U
Page 99 and 100:
Pattern: Fire and Forget • Contex
Page 101 and 102:
Pattern: Sync with Server • Conte
Page 103 and 104:
Pattern: Poll Object • Context: 1
Page 105 and 106:
Pattern: Result Callback • Contex
Page 107 and 108:
Pattern: Message Queue • Context:
Page 109 and 110:
Relations among the Patterns Acknow
Page 111 and 112:
Interactions: Sync with Server Clie
Page 113 and 114:
Interactions: Result Callback Clien
Page 115 and 116:
Technology Projections 115 Uwe Zdun
Page 117 and 118:
CORBA Technology Projection Name Se
Page 119 and 120:
Web Services • Definition: • A
Page 121 and 122:
Dynamic Invocation on Server Side O
Page 123 and 124:
Constructing an Invocation with a R
Page 125 and 126:
Marshalling • Conversion to SOAP
Page 127 and 128:
Message Processing (2) Client Clien
Page 129 and 130:
Example: Log Handler public class L
Page 131 and 132:
Protocol Integration • Heterogene
Page 133 and 134:
Client-Side Asynchrony • Axis doe
Page 135 and 136:
SAIWS - Invocation Handlers AsyncRe
Page 137 and 138:
SAIWS - Example: Result Callback In
Page 139 and 140:
Other Web Service Frameworks Discus
show all

Remoting patterns

Create successful ePaper yourself

Delete template?

Save as template?