tailieunhanh - Actors that Unify Threads and Events

We could not have wished for a more distinguished speaker to give the first lecture than Jeff Wall. Depiction, Object, Event, written especially for this occasion, is an original and thought-provoking interpretation of developments in the art of the last century that have culminated over the past two decades in an alleged fusion of art and life. Today, artists are often regarded as the trendsetting members of a ‘creative class’ that is fully integrated within the tertiary sector of the global economy. They are seen as fully-fledged service providers who meet all the requirements of professional entrepreneurship and contribute to the. | Actors that Unify Threads and Events Philipp Haller Martin Odersky LAMP-REPORT-2007-001 École Polytechnique Fédérale de Lausanne EPFL 1015 Lausanne Switzerland 1 Introduction Concurrency issues have lately received enormous interest because of two converging trends First multi-core processors make concurrency an essential ingredient of efficient program execution. Second distributed computing and web services are inherently concurrent. Message-based concurrency is attractive because it might provide a way to address the two challenges at the same time. It can be seen as a higher-level model for threads with the potential to generalize to distributed computation. Many message passing systems used in practice are instantiations of the actor model 1 11 12 . A popular implementation of this form of concurrency is the Erlang 3 programming language. Erlang supports massively concurrent systems such as telephone exchanges by using a very lightweight implementation of concurrent processes. On mainstream platforms such as the JVM 16 an equally attractive implementation was as yet missing. Their standard concurrency constructs shared-memory threads with locks suffer from high initialization and context-switching overhead as well as high memory consumption. Therefore the interleaving of independent computations is often modelled in an event-driven style on these platforms. However programming in an explicitly event-driven style is complicated and error-prone because it involves an inversion of control. In previous work 10 we developed event-based actors which let one program event-driven systems without inversion of control. Event-based actors support the same operations as thread-based actors except that the receive operation cannot return normally to the thread that invoked it. Instead the entire continuation of such an actor has to be a part of the receive operation. This makes it possible to model a suspended actor by a closure which is usually much cheaper than .

crossorigin="anonymous">
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.