DOCSLIB.ORG

Developer's Guide Sergey A

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Developer's Guide Sergey A Complex Event Processing with Triceps CEP v1.0 Developer's Guide Sergey A. Babkin Complex Event Processing with Triceps CEP v1.0 : Developer's Guide Sergey A. Babkin Copyright © 2011, 2012 Sergey A. Babkin All rights reserved. This manual is a part of the Triceps project. It is covered by the same Triceps version of the LGPL v3 license as Triceps itself. The author can be contacted by e-mail at <[email protected]> or <[email protected]>. Many of the designations used by the manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this manual, and the author was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this manual, the author assumes no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. Table of Contents 1. The field of CEP .................................................................................................................................. 1 1.1. What is the CEP? ....................................................................................................................... 1 1.2. The uses of CEP ........................................................................................................................ 2 1.3. Surveying the CEP langscape ....................................................................................................... 2 1.4. We're not in 1950s any more, or are we? ........................................................................................ 3 2. Enter Triceps ....................................................................................................................................... 7 2.1. What led to it ............................................................................................................................ 7 2.2. Hello, world! ............................................................................................................................. 8 3. Building Triceps ................................................................................................................................. 11 3.1. Downloading Triceps ................................................................................................................ 11 3.2. The reference environment ......................................................................................................... 11 3.3. The basic build ........................................................................................................................ 11 3.4. Building the documentation ........................................................................................................ 12 3.5. Running the examples and simple programs .................................................................................. 13 3.6. Installation of the Perl library ..................................................................................................... 14 3.7. Installation of the C++ library ..................................................................................................... 15 3.8. Disambiguation of the C++ library .............................................................................................. 16 3.9. Build configuration settings ........................................................................................................ 17 4. API Fundamentals ............................................................................................................................... 19 4.1. Languages and layers ................................................................................................................ 19 4.2. Errors, deaths and confessions .................................................................................................... 19 4.3. Memory management fundamentals ............................................................................................. 21 4.4. Triceps constants ...................................................................................................................... 22 4.5. Printing the object contents ........................................................................................................ 22 4.6. The Hungarian notation ............................................................................................................. 24 5. Rows ................................................................................................................................................ 25 5.1. Simple types ............................................................................................................................ 25 5.2. Row types ............................................................................................................................... 25 5.3. Row types equivalence .............................................................................................................. 27 5.4. Rows ...................................................................................................................................... 28 6. Labels and Row Operations .................................................................................................................. 31 6.1. Labels basics ........................................................................................................................... 31 6.2. Label construction .................................................................................................................... 32 6.3. Other label methods .................................................................................................................. 33 6.4. Row operations ........................................................................................................................ 34 6.5. Opcodes .................................................................................................................................. 36 7. Scheduling ......................................................................................................................................... 39 7.1. Overview of the scheduling ........................................................................................................ 39 7.2. No bundling ............................................................................................................................ 39 7.3. Basic scheduling in Triceps ........................................................................................................ 40 7.4. Loop scheduling ....................................................................................................................... 42 7.5. Execution unit .......................................................................................................................... 46 7.6. Error handling during the execution ............................................................................................. 50 7.7. The main loop ......................................................................................................................... 50 7.8. Main loop with a socket ............................................................................................................ 51 7.9. Example of a topological loop .................................................................................................... 56 7.10. Issues with the Triceps scheduling ............................................................................................. 59 7.11. Trays, or yes bundling ............................................................................................................. 60 7.12. Tracing the execution .............................................................................................................. 61 8. Memory Management .......................................................................................................................... 69 8.1. Reference cycles ....................................................................................................................... 69 8.2. Clearing of the labels ................................................................................................................ 70 8.3. The clearing labels .................................................................................................................... 71 iii 9. Tables ............................................................................................................................................... 73 9.1. Hello, tables! ........................................................................................................................... 73 9.2. Tables and labels ...................................................................................................................... 74 9.3. Basic iteration through the table .................................................................................................. 77 9.4. Deleting a row ......................................................................................................................... 77 9.5. A closer look at the RowHandles ................................................................................................ 78 9.6. A window is a FIFO ................................................................................................................. 80 9.7. Secondary indexes
Load more

Recommended publications
  • More Efficient Serialization and RMI for Java
    To appear in: Concurrency: Practice & Experience, Vol. 11, 1999. More Ecient Serialization and RMI for Java Michael Philippsen, Bernhard Haumacher, and Christian Nester Computer Science Department, University of Karlsruhe Am Fasanengarten 5, 76128 Karlsruhe, Germany [phlippjhaumajnester]@ira.u ka.de http://wwwipd.ira.uka.de/JavaPa rty/ Abstract. In current Java implementations, Remote Metho d Invo ca- tion RMI is to o slow, esp ecially for high p erformance computing. RMI is designed for wide-area and high-latency networks, it is based on a slow ob ject serialization, and it do es not supp ort high-p erformance commu- nication networks. The pap er demonstrates that a much faster drop-in RMI and an ecient drop-in serialization can b e designed and implemented completely in Java without any native co de. Moreover, the re-designed RMI supp orts non- TCP/IP communication networks, even with heterogeneous transp ort proto cols. We demonstrate that for high p erformance computing some of the ocial serialization's generality can and should b e traded for sp eed. Asaby-pro duct, a b enchmark collection for RMI is presented. On PCs connected through Ethernet, the b etter serialization and the improved RMI save a median of 45 maximum of 71 of the runtime for some set of arguments. On our Myrinet-based ParaStation network a cluster of DEC Alphas wesave a median of 85 maximum of 96, compared to standard RMI, standard serialization, and Fast Ethernet; a remote metho d invo cation runs as fast as 80 s round trip time, compared to ab out 1.5 ms.
    [Show full text]
  • Course Outlines
    COURSE NAME PYTHON PROGRAMMING OVERVIEW OBJECTIVES Python is a general-purpose, versatile, and popular How Python works and its place in the world of programming language. It is a great first language programming languages; to work with and because it is concise and easy to read, and it is also manipulate strings; to perform math operations; to a good language to have in any programmer’s stack work with Python sequences; to collect user input as it can be used for everything from web and output results; flow control processing; to write development to software development and scientific to, and read from, files; to write functions; to handle applications. exception; and work with dates and times. WHO SHOULD ATTEND PRE-REQUISITES Students new to the language. Some experience with other programming languages DELIVERY METHOD DURATION Instructor-led virtual course 5 days (40 hours) COURSE OUTLINE PYTHON INSTALLATION LOOPS Python Distributions (ActivePython, Anaconda, For(each) loop MiniConda) Absence of traditional for (i=0, i<n, i++) loop Additional Modules (Pip, conda, easy_install) Basic Examples with foreach loop PYTHON INTRODUCTION & BASICS Emulating Traditional for loops using range(n) The Python interpreter While Loops Working with command-line/IDE FUNCTIONS Python Data Types Def Keyword Built in operators, functions and methods Functions without args Data and type introspection basics: type (), dir() Functions with fixed num of args Syntax (Blocks and indentation) Functions with variable number of args and default Concepts (Scope,
    [Show full text]
  • Reflecting on an Existing Programming Language
    Vol. 6, No. 9, Special Issue: TOOLS EUROPE 2007, October 2007 Reflecting on an Existing Programming Language Andreas Leitner, Dept. of Computer Science, ETH Zurich, Switzerland Patrick Eugster, Dept. of Computer Science, Purdue University, USA Manuel Oriol, Dept. of Computer Science, ETH Zurich, Switzerland Ilinca Ciupa, Dept. of Computer Science, ETH Zurich, Switzerland Reflection has proven to be a valuable asset for programming languages, es- pecially object-oriented ones, by promoting adaptability and extensibility of pro- grams. With more and more applications exceeding the boundary of a single address space, reflection comes in very handy for instance for performing con- formance tests dynamically. The precise incentives and thus mechanisms for reflection vary strongly between its incarnations, depending on the semantics of the considered programming lan- guage, the architecture of its runtime environment, safety and security concerns, etc. Another strongly influential factor is legacy, i.e., the point in time at which the corresponding reflection mechanisms are added to the language. This parameter tends to dictate the feasible breadth of the features offered by an implementation of reflection. This paper describes a pragmatic approach to reflection, consisting in adding introspection to an existing object-oriented programming language a posteriori, i.e., without extending the programming language, compiler, or runtime environ- ment in any specific manner. The approach consists in a pre-compiler generating specific code for types which are to be made introspectable, and an API through which this code is accessed. We present two variants of our approach, namely a homogeneous approach (for type systems with a universal root type) and a heterogeneous approach (without universal root type), and the corresponding generators.
    [Show full text]
  • An Organized Repository of Ethereum Smart Contracts' Source Codes and Metrics
    Article An Organized Repository of Ethereum Smart Contracts’ Source Codes and Metrics Giuseppe Antonio Pierro 1,* , Roberto Tonelli 2,* and Michele Marchesi 2 1 Inria Lille-Nord Europe Centre, 59650 Villeneuve d’Ascq, France 2 Department of Mathematics and Computer Science, University of Cagliari, 09124 Cagliari, Italy; [email protected] * Correspondence: [email protected] (G.A.P.); [email protected] (R.T.) Received: 31 October 2020; Accepted: 11 November 2020; Published: 15 November 2020 Abstract: Many empirical software engineering studies show that there is a need for repositories where source codes are acquired, filtered and classified. During the last few years, Ethereum block explorer services have emerged as a popular project to explore and search for Ethereum blockchain data such as transactions, addresses, tokens, smart contracts’ source codes, prices and other activities taking place on the Ethereum blockchain. Despite the availability of this kind of service, retrieving specific information useful to empirical software engineering studies, such as the study of smart contracts’ software metrics, might require many subtasks, such as searching for specific transactions in a block, parsing files in HTML format, and filtering the smart contracts to remove duplicated code or unused smart contracts. In this paper, we afford this problem by creating Smart Corpus, a corpus of smart contracts in an organized, reasoned and up-to-date repository where Solidity source code and other metadata about Ethereum smart contracts can easily and systematically be retrieved. We present Smart Corpus’s design and its initial implementation, and we show how the data set of smart contracts’ source codes in a variety of programming languages can be queried and processed to get useful information on smart contracts and their software metrics.
    [Show full text]
  • Flexible Composition for C++11
    Maximilien de Bayser Flexible Composition for C++11 Disserta¸c~aode Mestrado Dissertation presented to the Programa de P´os-Gradua¸c~ao em Inform´atica of the Departamento de Inform´atica, PUC-Rio as partial fulfillment of the requirements for the degree of Mestre em Inform´atica. Advisor: Prof. Renato Fontoura de Gusm~ao Cerqueira Rio de Janeiro April 2013 Maximilien de Bayser Flexible Composition for C++11 Dissertation presented to the Programa de P´os-Gradua¸c~ao em Inform´atica of the Departamento de Inform´atica, PUC-Rio as partial fulfillment of the requirements for the degree of Mestre em Inform´atica. Approved by the following commission: Prof. Renato Fontoura de Gusm~aoCerqueira Advisor Pontif´ıcia Universidade Cat´olica do Rio de Janeiro Prof. Alessandro Garcia Department of Informatics { PUC-Rio Prof. Waldemar Celes Department of Informatics { PUC-Rio Prof. Jos´eEugenio Leal Coordinator of the Centro T´ecnico Cient´ıfico Pontif´ıcia Universidade Cat´olica do Rio de Janeiro Rio de Janeiro | April 4th, 2013 All rights reserved. It is forbidden partial or complete reproduction without previous authorization of the university, the author and the advisor. Maximilien de Bayser Maximilien de Bayser graduated from PUC-Rio in Computer Engineering. He is also working at the Research Center for Inspection Technology where he works on software for non- destructive testing of oil pipelines and flexible risers for PE- TROBRAS. Bibliographic data de Bayser, Maximilien Flexible Composition for C++11 / Maximilien de Bayser; advisor: Renato Fontoura de Gusm~ao Cerqueira . | 2013. 107 f. : il. ; 30 cm 1. Disserta¸c~ao(Mestrado em Inform´atica) - Pontif´ıcia Universidade Cat´olica do Rio de Janeiro, Rio de Janeiro, 2013.
    [Show full text]
  • Objective-C Fundamentals
    Christopher K. Fairbairn Johannes Fahrenkrug Collin Ruffenach MANNING Objective-C Fundamentals Download from Wow! eBook <www.wowebook.com> Download from Wow! eBook <www.wowebook.com> Objective-C Fundamentals CHRISTOPHER K. FAIRBAIRN JOHANNES FAHRENKRUG COLLIN RUFFENACH MANNING SHELTER ISLAND Download from Wow! eBook <www.wowebook.com> For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. 20 Baldwin Road PO Box 261 Shelter Island, NY 11964 Email: [email protected] ©2012 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled
    [Show full text]
  • Objective-C Language and Gnustep Base Library Programming Manual
    Objective-C Language and GNUstep Base Library Programming Manual Francis Botto (Brainstorm) Richard Frith-Macdonald (Brainstorm) Nicola Pero (Brainstorm) Adrian Robert Copyright c 2001-2004 Free Software Foundation Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the above conditions for modified versions. i Table of Contents 1 Introduction::::::::::::::::::::::::::::::::::::: 3 1.1 What is Object-Oriented Programming? :::::::::::::::::::::::: 3 1.1.1 Some Basic OO Terminology :::::::::::::::::::::::::::::: 3 1.2 What is Objective-C? :::::::::::::::::::::::::::::::::::::::::: 5 1.3 History :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 1.4 What is GNUstep? ::::::::::::::::::::::::::::::::::::::::::::: 6 1.4.1 GNUstep Base Library :::::::::::::::::::::::::::::::::::: 6 1.4.2 GNUstep Make Utility :::::::::::::::::::::::::::::::::::: 7 1.4.3 A Word on the Graphical Environment :::::::::::::::::::: 7 1.4.4 The GNUstep Directory Layout ::::::::::::::::::::::::::: 7 1.5 Building Your First Objective-C Program :::::::::::::::::::::: 8 2 The Objective-C Language :::::::::::::::::::
    [Show full text]
  • A Sequel to the Static C++ Object-Oriented Programming Paradigm (SCOOP 2)
    Semantics-Driven Genericity: A Sequel to the Static C++ Object-Oriented Programming Paradigm (SCOOP 2) Thierry G´eraud,Roland Levillain EPITA Research and Development Laboratory (LRDE) 14-16, rue Voltaire, FR-94276 Le Kremlin-Bic^etreCedex, France [email protected], [email protected] Web Site: http://www.lrde.epita.fr Abstract. Classical (unbounded) genericity in C++03 defines the inter- actions between generic data types and algorithms in terms of concepts. Concepts define the requirements over a type (or a parameter) by ex- pressing constraints on its methods and dependent types (typedefs). The upcoming C++0x standard will promote concepts from abstract en- tities (not directly enforced by the tools) to language constructs, enabling compilers and tools to perform additional checks on generic constructs as well as enabling new features (e.g., concept-based overloading). Most modern languages support this notion of signature on generic types. How- ever, generic types built on other types and relying on concepts|to both ensure type conformance and drive code specialization|restrain the in- terface and the implementation of the newly created type: specific meth- ods and associated types not mentioned in the concept will not be part of the new type. The paradigm of concept-based genericity lacks the re- quired semantics to transform types while retaining or adapting their intrinsic capabilities. We present a new form of semantically-enriched genericity allowing static, generic type transformations through a sim- ple form of type introspection based on type metadata called properties. This approach relies on a new Static C++ Object-Oriented Programming (Scoop) paradigm, and is adapted to the creation of generic and efficient libraries, especially in the field of scientific computing.
    [Show full text]
  • Efficient Data Communication Between a Webclient and a Cloud Environment
    Kit Gustavsson & Erik Stenlund Efficient data communication between a webclient and a cloud environment a cloud and webclient a between communication data Efficient Master’s Thesis Efficient data communication between a webclient and a cloud environment Kit Gustavsson Erik Stenlund Series of Master’s theses Department of Electrical and Information Technology LU/LTH-EIT 2016-528 http://www.eit.lth.se Department of Electrical and Information Technology, Faculty of Engineering, LTH, Lund University, 2016. Efficient data communication between a webclient and a cloud environment Kit Gustavsson [email protected] Erik Stenlund [email protected] Axis Communications Emdalavägen 14 Advisor: Maria Kihl June 23, 2016 Printed in Sweden E-huset, Lund, 2016 Abstract Modern single page web applications that continuously transfer a lot of data be- tween the clients and the server require new techniques for communicating this data. The REST architecture has for a long time been the most common solu- tion when developing web APIs but the technique GraphQL has in recent time become an interesting alternative to REST. This thesis had two major purposes, the first was to investigate and point out the difference between using REST and a GraphQL solution when developing a web API. The second was to, based on the results of the investigation, create a decision model that may be used as support when deciding on what type of tech- nique to use and the effect of the decision when developing a web application. Prototypes of each API were implemented and used to conduct measurements of each technique’s performance. Additional infrastructure such as web servers and load generators were also developed for the measurements.
    [Show full text]
  • The Objective-C Programming Language
    Inside Mac OS X The Objective-C Programming Language February 2003 Apple Computer, Inc. Even though Apple has reviewed this © 2002 Apple Computer, Inc. manual, APPLE MAKES NO All rights reserved. WARRANTY OR REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH No part of this publication may be RESPECT TO THIS MANUAL, ITS reproduced, stored in a retrieval QUALITY, ACCURACY, system, or transmitted, in any form or MERCHANTABILITY, OR FITNESS by any means, mechanical, electronic, FOR A PARTICULAR PURPOSE. AS A photocopying, recording, or RESULT, THIS MANUAL IS SOLD “AS otherwise, without prior written IS,” AND YOU, THE PURCHASER, ARE permission of Apple Computer, Inc., ASSUMING THE ENTIRE RISK AS TO with the following exceptions: Any ITS QUALITY AND ACCURACY. person is hereby authorized to store documentation on a single computer IN NO EVENT WILL APPLE BE LIABLE for personal use only and to print FOR DIRECT, INDIRECT, SPECIAL, copies of documentation for personal INCIDENTAL, OR CONSEQUENTIAL use provided that the documentation DAMAGES RESULTING FROM ANY contains Apple’s copyright notice. DEFECT OR INACCURACY IN THIS The Apple logo is a trademark of MANUAL, even if advised of the Apple Computer, Inc. possibility of such damages. Use of the “keyboard” Apple logo THE WARRANTY AND REMEDIES SET (Option-Shift-K) for commercial FORTH ABOVE ARE EXCLUSIVE AND purposes without the prior written IN LIEU OF ALL OTHERS, ORAL OR consent of Apple may constitute WRITTEN, EXPRESS OR IMPLIED. No trademark infringement and unfair Apple dealer, agent, or employee is competition in violation of federal authorized to make any modification, and state laws.
    [Show full text]
  • Arxiv:2003.07798V3 [Cs.MS] 1 Sep 2021
    PRESSIO: ENABLING PROJECTION-BASED MODEL REDUCTION FOR LARGE-SCALE NONLINEAR DYNAMICAL SYSTEMS ∗ FRANCESCO RIZZI† , PATRICK J. BLONIGAN‡ , ERIC J. PARISH‡ , AND KEVIN T. CARLBERG‡§ Abstract. This work introduces Pressio, an open-source project aimed at enabling leading- edge projection-based reduced order models (ROMs) for large-scale nonlinear dynamical systems in science and engineering. Pressio provides model-reduction methods that can reduce both the num- ber of spatial and temporal degrees of freedom for any dynamical system expressible as a system of parameterized ordinary differential equations (ODEs). We leverage this simple, expressive mathe- matical framework as a pivotal design choice to enable a minimal application programming interface (API) that is natural to dynamical systems. The core component of Pressio is a C++11 header-only library that leverages generic programming to support applications with arbitrary data types and arbitrarily complex programming models. This is complemented with Python bindings to expose these C++ functionalities to Python users with negligible overhead and no user-required binding code. We discuss the distinguishing characteristics of Pressio relative to existing model-reduction libraries, outline its key design features, describe how the user interacts with it, and present two test cases—including one with over 20 million degrees of freedom—that highlight the performance results of Pressio and illustrate the breath of problems that can be addressed with it. Key words. projection-based model reduction, Galerkin, LSPG, POD, SVD, sample mesh, hyper-reduction, scientific computing, object-oriented programming, generic programming, policy- based design, design by introspection, template metaprogramming, HPC, Kokkos, Trilinos, Python. AMS subject classifications. 65L05, 65L06, 65M12, 68U20, 68N15, 68W10, 68W15, 68N01, 76K05 1.
    [Show full text]
  • Summary: Using Refletion to Break Encapsulation
    Summary: Using Refletion To Break Encapsulation Programs try to insulate the internal structure of their classes from their public interfaces by implementing the principle of encapsulation. Using Reflection, we can not only find out about a class's internal structure; we can access and modify their private properties as well. This presentation will give a cursory overview of the principle of encapsulation. It will also show basic examples of how to access and modify private variables of another class using reflection, and how to invoke private functions of another class. *source code: All the slides that use main(), are in the Main.java. There are commented out sections for each different main() that were used in the slides Breaking Encapsulation By Using Reflection by Drew Goldberg reference: http://en.wikipedia.org/wiki/File:Russian_Dolls.jpg What Is Encapuslation? "Encapsulation: Encapsulation refers to a set of language- level mechanisms or design techniques that hide implementation details of a class, module, or subsystem from other classes, modules, and subsystems." reference: http://www.cs.colorado.edu/~kena/classes/5448/f12/lectures/02- ooparadigm.pdf Why Is Encapsulation Important? Encapsulation enables a class to modify its internal state without having to modify it public interface. This means that a class's internal structure can be changed without breaking other classes using it's public interface. Encapsulation also protects the class for other classes modifying it's internal state. reference: http://stackoverflow.com/questions/3982844/encapsulation-well-designed-class Simple Example Of Encapsulations Some basic types of encapsulation are making variables private. Allowing access to these variables via getter and setter functions.
    [Show full text]