Asynchronous Completion Token - Ingeniørhøjskolen i Århus

More documents

Recommendations

Info

$Course Material\Efficiently Coding Communication Protocols in C++ ...$

2. Select a Strategy for holding the ACT at the Initiator • Implicit ACTs – Defining it to be the address of the initiator completion handler object – Benefits: efficient time and space utilization • Explicit ACTs – The initiator hold its ACTs in an explicit data structure • for example a table of completion handlers – Benefits: increased robustness and authenticity • Initiators are responsible for freeing any resources associated with ACTs © Ingeniørhøjskolen i Århus Slide 10
6. Determine the initiator demultiplexing strategy 1. Queued completion events – ACTs is placed in a completion event queue by a service or by a local service proxy – An initiator removes the ACT from a completion event queue – As shown in the Proactor pattern description (see next slide) 2. Callbacks – An initiator passes a callback function/object to the service – The ACTs can be returned as a parameter to the callback object (can often be a Singleton) © Ingeniørhøjskolen i Århus Slide 11
Page 1 and 2: Distributed Real-Time Systems (TI-D
Page 3 and 4: Context • An event-driven system
Page 5 and 6: Solution • Together with each asy
Page 7 and 8: Sequence Diagram :Initiator :Comple
Page 9: 1. Define the ACT Representation
Page 13 and 14: 6.1 Async_Stream_Read_Result (ACT)
Page 15 and 16: Management Example (1) 2 Window 2 L
Page 17 and 18: Management Example (3) class Manage
Page 19 and 20: Management Example (5) int main() {
Page 21 and 22: ACT Liabilities • Memory leaks -
Page 23: Relation to other POSA2 Patterns ©

Asynchronous Completion Token - Ingeniørhøjskolen i Århus

Create successful ePaper yourself

Delete template?

Save as template?