Programming Model and Protocols for Reconfigurable Distributed ...

More documents

Recommendations

Info

30 CHAPTER 2. COMPONENT MODEL When a Request event is triggered by a client, as the event passes through different channels and ports in the architecture, it saves them on an internal stack. When the server component generates a Response event, it initializes it with the Request’s stack. As the Response event is passed through the architecture, the run-time system pops its stack one element at a time to see where to deliver it next. This mechanism, ensures that only the client which initiated a Request will receive the corresponding Response. 2.6 Component Initialization and Life Cycle Every component provides a special Control port used for initialization, life cycle, and fault management. Figure 2.11 illustrates the Control port type and a component that declares an Init, a Start, and a Stop handler. Typically, for each component definition that requires state initialization, we define a specific initialization event, as a subtype of Init, which contains component-specific configuration parameters. startH Start + Control stopH Stop MyComponent initH MyInit + Control MyInit Init + Fault Started Stopped Start Stop Init Figure 2.11. Every Kompics component provides a Control port by default. To this Control port, the component can subscribe Start, Stop, and Init handlers. In general, we do not illustrate the control port in component diagrams. An Init event is guaranteed to be the first event handled by a component. When a component subscribes an Init event handler to its Control port in its constructor, the run-time system will only schedule the component for execution upon receiving an Init event. Start and Stop events allow a component which handles them to take some actions when the component is activated or passivated. A component is created passive. In the passive state, a component can receive events but it will not execute them. (Received events are stored in a port queue.) When activated, a component will enter the active state executing any enqueued events. Handling life cycle events (illustrated in Code 2.10) is optional.
2.6. COMPONENT INITIALIZATION AND LIFE CYCLE 31 Code 2.10 Handling component initialization and life cycle events 1 class MyComponent extends ComponentDefinition { 2 int myParameter; 3 public MyComponent() { // ← component constructor 4 subscribe(handleStart, control); // ←similar for Stop 5 subscribe(handleInit, control); 6 } 7 Handler handleInit = new Handler() { 8 public void handle(MyInit init) { 9 myParameter = init.myParameter; 10 } 11 }; 12 Handler handleStart = new Handler() { 13 public void handle(Start event) { 14 System.out.println("started"); 15 } 16 }; 17 } To activate a component, an enclosing composite component triggers Start event on the Control port of the subcomponent as shown in Code 2.11. Similarly, parent components can initialize or passivate their children by triggering Init or respectively Stop events, on their control ports. Code 2.11 Triggering component initialization and life cycle events 1 trigger(new MyInit(42), myComponent.control()); 2 trigger(new Start(), myComponent.control()); 3 trigger(new Stop(), myComponent.control()); When a composite component is activated (or passivated), its subcomponents are recursively activated (or passivated). The bootstrap construct, introduced in the Main component example (see Code 2.7), both creates and starts the Main component, recursively creating and starting all components. When a composite component needs to perform dynamic reconfiguration on some of its subcomponents, it passivates them first (see Section 2.9). Once the parent component has triggered a Stop event on a subcomponent’s Control port it does not mean that the subcomponent has already been passivated since handling the Stop event happens asynchronously.
Page 1: Programming Model and Protocols for
Page 5 and 6: Programming Model and Protocols for
Page 7: Abstract Distributed systems are ev
Page 11 and 12: Acknowledgements I am truly honoure
Page 13 and 14: Contents List of Figures List of So
Page 15 and 16: CONTENTS xiii 4.4 Testing and Debug
Page 17 and 18: List of Figures 2.1 An example of p
Page 19 and 20: List of Source Code Listings 2.1 A
Page 21 and 22: Chapter 1 Introduction A large and
Page 23 and 24: 1.1. MOTIVATION 3 1.1 Motivation Mo
Page 25 and 26: 1.3. THESIS CONTRIBUTIONS 5 This fa
Page 27 and 28: 1.3. THESIS CONTRIBUTIONS 7 systems
Page 29 and 30: 1.5. ORGANIZATION 9 • Cosmin Arad
Page 31: 1.5. ORGANIZATION 11 admits efficie
Page 35 and 36: Chapter 2 Component Model Kompics i
Page 37 and 38: 2.1. CONCEPTS IN KOMPICS 17 specifi
Page 39 and 40: 2.1. CONCEPTS IN KOMPICS 19 + + F
Page 41 and 42: 2.1. CONCEPTS IN KOMPICS 21 MyCompo
Page 43 and 44: 2.2. KOMPICS OPERATIONS 23 Code 2.7
Page 45 and 46: 2.3. PUBLISH-SUBSCRIBE MESSAGE PASS
Page 47 and 48: 2.4. CHANNEL EVENT FILTERING 27 Fig
Page 49: 2.5. REQUEST-RESPONSE INTERACTION 2
Page 53 and 54: 2.8. NON-BLOCKING RECEIVE 33 + som
Page 55: 2.9. DYNAMIC RECONFIGURATION 35 2.9
Page 58 and 59: 38 CHAPTER 3. PROGRAMMING PATTERNS
Page 74 and 75: 54 CHAPTER 4. IMPLEMENTATION ASPECT
Page 100 and 101:
80 CHAPTER 4. IMPLEMENTATION ASPECT
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
86 CHAPTER 5. KOMPICS DISCUSSION AN
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 115 and 116:
Chapter 6 Background, Motivation, a
Page 117 and 118:
CHAPTER 6. BACKGROUND, MOTIVATION,
Page 119 and 120:
6.2. CONSISTENCY, AVAILABILITY, AND
Page 121 and 122:
6.4. QUORUM-BASED REPLICATION SYSTE
Page 123:
6.5. PROBLEM STATEMENT 103 5 10 15
Page 126 and 127:
106 CHAPTER 7. CONSISTENT QUORUMS g
Page 128 and 129:
108 CHAPTER 7. CONSISTENT QUORUMS A
Page 130 and 131:
110 CHAPTER 7. CONSISTENT QUORUMS v
Page 132 and 133:
112 CHAPTER 7. CONSISTENT QUORUMS b
Page 134 and 135:
114 CHAPTER 7. CONSISTENT QUORUMS A
Page 136 and 137:
116 CHAPTER 7. CONSISTENT QUORUMS v
Page 138 and 139:
118 CHAPTER 7. CONSISTENT QUORUMS t
Page 140 and 141:
120 CHAPTER 7. CONSISTENT QUORUMS C
Page 142 and 143:
122 CHAPTER 7. CONSISTENT QUORUMS F
Page 144 and 145:
124 CHAPTER 8. CATS SYSTEM ARCHITEC
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 159 and 160:
Chapter 9 Scalability, Elasticity,
Page 161 and 162:
9.2. THROUGHPUT AND LATENCY 141 Thr
Page 163 and 164:
9.3. SCALABILITY 143 Throughput [10
Page 165 and 166:
9.5. OVERHEAD OF CONSISTENT QUORUMS
Page 167 and 168:
9.5. OVERHEAD OF CONSISTENT QUORUMS
Page 169 and 170:
9.6. COMPARISON WITH CASSANDRA 149
Page 171 and 172:
Chapter 10 CATS Discussion and Comp
Page 173 and 174:
10.2. SEQUENTIAL CONSISTENCY AT SCA
Page 175 and 176:
10.6. SCALABLE AND CONSISTENT KEY-V
Page 177 and 178:
Chapter 11 Conclusions We are witne
Page 179 and 180:
CHAPTER 11. CONCLUSIONS 159 replica
Page 181 and 182:
11.1. KOMPICS LIMITATIONS AND LESSO
Page 183 and 184:
11.2. CATS LIMITATIONS AND LESSONS
Page 185 and 186:
11.3. FUTURE WORK 165 distribution
Page 187 and 188:
Appendix A Kompics Abstract Syntax
Page 189:
APPENDIX A. KOMPICS ABSTRACT SYNTAX
Page 192 and 193:
172 APPENDIX B. KOMPICS OPERATIONAL
Page 194 and 195:
Page 196 and 197:
Page 199 and 200:
Bibliography [1] Daniel Abadi. Cons
Page 201 and 202:
BIBLIOGRAPHY 181 [16] Cosmin Arad,
Page 203 and 204:
BIBLIOGRAPHY 183 [38] Kenneth P. Bi
Page 205 and 206:
BIBLIOGRAPHY 185 [59] Brian F. Coop
Page 207 and 208:
BIBLIOGRAPHY 187 [77] Patrick Th. E
Page 209 and 210:
BIBLIOGRAPHY 189 [98] Vassos Hadzil
Page 211 and 212:
BIBLIOGRAPHY 191 [120] David Karger
Page 213 and 214:
BIBLIOGRAPHY 193 [142] Wyatt Lloyd,
Page 215 and 216:
BIBLIOGRAPHY 195 [164] Salman Niazi
Page 217 and 218:
BIBLIOGRAPHY 197 [186] Rackspace Cl
Page 219 and 220:
BIBLIOGRAPHY 199 [205] Yair Sovran,
Page 221:
BIBLIOGRAPHY 201 [226] András Varg
Page 224 and 225:
204 ACRONYMS DES discrete-event sim
Page 226 and 227:
206 ACRONYMS SMART Service Migratio
Page 228 and 229:
208 SICS DISSERTATION SERIES 9. Lar
Page 230 and 231:
210 SICS DISSERTATION SERIES 40. Ma
Page 232:
Colophon This dissertation was type
show all

Programming Model and Protocols for Reconfigurable Distributed ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?