DOCSLIB.ORG

Object-Oriented Programming Across Native-Virtual Boundaries

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Object-Oriented Programming Across Native-Virtual Boundaries Object-Oriented Programming across Native-Virtual Boundaries Paul Werbicki Rob Kremer Computer Science Department Computer Science Department University of Calgary University of Calgary 2500 University Dr., NW, 2500 University Dr., NW, Calgary, Canada, T2N 1N4 Calgary, Canada, T2N 1N4 1-403-2841718 1-403-2205112 [email protected] [email protected] [email protected] ABSTRACT Keywords There exist many implementations of object-oriented Native-virtual boundary, interoperability, object integration, C++, programming languages that execute on virtual computers which Java, Java Virtual Machine, Java Native Interface, design abstract from native host environments. These languages provide patterns. developers with a highly mobile platform where applications may easily execute on multiple environments. However, there exist situations where it is not possible to abstract from the host 1. INTRODUCTION environment, forcing the developer to program at least part of the One of the tenets of interpreted programming languages, Java in application specifically to a specific environment. Developing a particular, is the ability to develop and compile software once and single application using both native and virtual code allows those have it execute, without modification, on all environments mobile portions to remain abstracted from the environment while supported by the virtual machine [4]. To achieve this, the at the same time providing the required native access. software must generally be written entirely in the interpreted programming language. In some applications, however, it may be This paper discusses using object-oriented programming to allow necessary to have portions of the software highly mobile, while the use of C++ and Java in a single application. A class library, other portions must take advantage of optimizations only developed as part of the investigation, is used to enhance the provided on a single native host environment. native-virtual boundary interface and provide the developer with support for the use of objects. By examining how the library A practical example of this type of application exists in the area of works it is possible to gauge the level of support currently Multi-Agent Systems (MAS). In these types of applications, all available for this technique. An analysis of the available support agent processes need to communicate regardless of the highlights where virtual machines need to provide additional environment in which they execute, but some provide services functionality to fully enable this method of programming. and use resources only available on specific operating systems and hardware platforms. Some components of each entity, specifically the communications library, benefit from being Categories and Subject Descriptors mobile without having to be ported to each new environment. D.3 [ Software ]: Programming Languages; D.1.5 [ Programming However, it may not be possible to port the entire agent. Techniques ]: Object-oriented Programming; D.2.3 [ Software Engineering ]: Coding Tools and Techniques – Object-oriented Some virtual machines provide methods for integrating both Programming ; D.3.4 [ Programming Languages ]: Processors - virtual code and native code within the same program. The Java Interpreters Virtual Machine (JVM) with its Java Native Interface (JNI) is a good example. Using the JNI it is possible to make calls into mobile components of the application without having to write the General Terms entire program in an interpreted programming language [5]. The Experimentation, Standardization, Languages. JNI exposes a set of C functions that provide a low-level method of manipulating, controlling and executing code compiled to run on the virtual machine. The JVM executes in the same process space and interacts with native code across the native-virtual Permission to make digital or hard copies of all or part of this work for boundary defined by the JNI. personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that The procedural approach used by the JNI does not lend itself well copies bear this notice and the full citation on the first page. To copy to using mobile code written as an object-oriented library. Instead otherwise, or republish, to post on servers or to redistribute to lists, of accessing objects using procedural-style JNI functions, it is requires prior specific permission and/or a fee. highly desirable from a software engineering standpoint to treat Virtual Execution Environments (Vee’05) , June 11-12, 2005, Chicago, these interpreted objects as normal objects within the native Illinois, USA. Copyright 200 5 ACM 1 -58113 -000 -0/00/0004…$5.00. portions of the application. To investigate this approach, JavaCOM [11] was developed, a class library written in C++ all supporting libraries and third-party software provided by under the Microsoft Windows family of operating systems. The all of the programming languages used in the application. use of JavaCOM makes it somewhat possible to treat objects 3. Single language for library/API development . Due to the within an interpreted library as objects within a C++ application increased access to supporting libraries, researchers and or as components within the Component Object Model (COM) third-party software developers do not need to support [6] in languages such as Microsoft Visual Basic and C++. different version of their software, one for each programming language they need to support. Instead they can concentrate This paper describes the challenges of trying to integrate on creating a single, mobile language API and allow the end- interpreted objects and native objects within the same application. user to integrate this into their application by integrating the The goal of this research is to attempt to achieve complete re-use programming language in which it was developed. of an object-oriented communication library for Multi-Agent 4. Code reuse without access to the original source code . In Systems written in Java within an agent application developed in situations where applications are being ported from one C++. In doing so the hope is to discover ways to achieve object- language to another (such as in legacy systems) the original oriented development using interpreted and native code within the source code may not be available. In cases like this it is same process. Where this is not possible, the goal is to propose possible to contain the original code and use it directly, requirements of virtual machines needed to support such instead of re-writing it and potentially introducing errors. applications. 5. Integration of specialized operating system components, hardware platform components and legacy software . 1.1 Paper Overview Accessing specialized components and integrating with This paper is structured as follows. Section 2 specifies the legacy systems is common in Software Engineering. problem further, providing reasons why it is desirable to mix Combining native and virtual code makes it possible to use native and interpreted code and introduces an application that these exiting pieces from newer programming languages. benefits from such a scenario. Section 3 outlines approaches used to contain the JVM in a native application. Section 4 describes With the popularity of new object-oriented programming the JavaCOM class library and how it abstracts from the JNI languages, such as Java, that are free from any procedural heritage using design patterns to achieve a level of integration. Section 5 (unlike C++) more code is begin developed and shared in analyses how JavaCOM use of proxy classes provides support for languages that promote only object-oriented development. object-oriented programming between C++ and Java. Section 6 Integration of these libraries into a native application using a presents requirements for the JVM and virtual machines in procedural interface, such as the JNI, is awkward. It breaks down general to fully support object-oriented programming. We the object-oriented paradigm [9] making it difficult for the conclude with the benefits this research has for software developer to write a “good” program. engineering in general and future work in this area. If a language is said to support object-oriented programming then it must provide facilities to make it easy to program using objects. 2. PROBLEM SPECIFICATION Even though two programming languages both support object- The ability to integrate libraries written in an interpreted oriented programming it may be difficult for the flow of control to programming language (such as Java) into an application written 1 pass from the first programming language to the second. This in a native programming language presents some interesting interaction may take exceptional effort or skill on behalf of the opportunities in software development. Interoperability between developer and merely enable the use of multiple programming programming languages impacts many aspects of an application’s languages within a single application, but not support it. To fully development cycle, from initial design decisions, to the cost of support object-oriented programming using multiple maintaining the completed application. From a software programming languages there must be support for making it easy engineering viewpoint, some obvious advantages include: to integrate objects. 1. Decreased need to choose a single programming language Support for object-oriented development
Load more

Recommended publications
  • Jeannie: Granting Java Native Interface Developers Their Wishes
    Jeannie: Granting Java Native Interface Developers Their Wishes Martin Hirzel Robert Grimm IBM Watson Research Center New York University [email protected] [email protected] Abstract higher-level languages and vice versa. For example, a Java Higher-level languages interface with lower-level languages project can reuse a high-performance C library for binary such as C to access platform functionality, reuse legacy li- decision diagrams (BDDs) through the Java Native Inter- braries, or improve performance. This raises the issue of face [38] (JNI), which is the standard FFI for Java. how to best integrate different languages while also recon- FFI designs aim for productivity, safety, portability, and ciling productivity, safety, portability, and efficiency. This efficiency. Unfortunately, these goals are often at odds. For paper presents Jeannie, a new language design for integrat- instance, Sun’s original FFI for Java, the Native Method In- ing Java with C. In Jeannie, both Java and C code are nested terface [52, 53] (NMI), directly exposed Java objects as C within each other in the same file and compile down to JNI, structs and thus provided simple and fast access to object the Java platform’s standard foreign function interface. By fields. However, this is unsafe, since C code can violate Java combining the two languages’ syntax and semantics, Jean- types, notably by storing an object of incompatible type in a nie eliminates verbose boiler-plate code, enables static error field. Furthermore, it constrains garbage collectors and just- detection across the language boundary, and simplifies dy- in-time compilers, since changes to the data representation namic resource management.
    [Show full text]
  • JNI – C++ Integration Made Easy
    JNI – C++ integration made easy Evgeniy Gabrilovich Lev Finkelstein [email protected] [email protected] Abstract The Java Native Interface (JNI) [1] provides interoperation between Java code running on a Java Virtual Machine and code written in other programming languages (e.g., C++ or assembly). The JNI is useful when existing libraries need to be integrated into Java code, or when portions of the code are implemented in other languages for improved performance. The Java Native Interface is extremely flexible, allowing Java methods to invoke native methods and vice versa, as well as allowing native functions to manipulate Java objects. However, this flexibility comes at the expense of extra effort for the native language programmer, who has to explicitly specify how to connect to various Java objects (and later to disconnect from them, to avoid resource leak). We suggest a template-based framework that relieves the C++ programmer from most of this burden. In particular, the proposed technique provides automatic selection of the right functions to access Java objects based on their types, automatic release of previously acquired resources when they are no longer necessary, and overall simpler interface through grouping of auxiliary functions. Introduction The Java Native Interface1 is a powerful framework for seamless integration between Java and other programming languages (called “native languages” in the JNI terminology). A common case of using the JNI is when a system architect wants to benefit from both worlds, implementing communication protocols in Java and computationally expensive algorithmic parts in C++ (the latter are usually compiled into a dynamic library, which is then invoked from the Java code).
    [Show full text]
  • T U M a Digital Wallet Implementation for Anonymous Cash
    Technische Universität München Department of Informatics Bachelor’s Thesis in Information Systems A Digital Wallet Implementation for Anonymous Cash Oliver R. Broome Technische Universität München Department of Informatics Bachelor’s Thesis in Information Systems A Digital Wallet Implementation for Anonymous Cash Implementierung eines digitalen Wallets for anonyme Währungen Author Oliver R. Broome Supervisor Prof. Dr.-Ing. Georg Carle Advisor Sree Harsha Totakura, M. Sc. Date October 15, 2015 Informatik VIII Chair for Network Architectures and Services I conrm that this thesis is my own work and I have documented all sources and material used. Garching b. München, October 15, 2015 Signature Abstract GNU Taler is a novel approach to digital payments with which payments are performed with cryptographically generated representations of actual currencies. The main goal of GNU Taler is to allow taxable anonymous payments to non-anonymous merchants. This thesis documents the implementation of the Android version of the GNU Taler wallet, which allows users to create new Taler-based funds and perform payments with them. Zusammenfassung GNU Taler ist ein neuartiger Ansatz für digitales Bezahlen, bei dem Zahlungen mit kryptographischen Repräsentationen von echten Währungen getätigt werden. Das Hauptziel von GNU Taler ist es, versteuerbare, anonyme Zahlungen an nicht-anonyme Händler zu ermöglichen. Diese Arbeit dokumentiert die Implementation der Android-Version des Taler-Portemonnaies, der es Benutzern erlaubt, neues Taler-Guthaben zu erzeugen und mit ihnen Zahlungen zu tätigen. I Contents 1 Introduction 1 1.1 GNU Taler . .2 1.2 Goals of the thesis . .2 1.3 Outline . .3 2 Implementation prerequisites 5 2.1 Native libraries . .5 2.1.1 Libgcrypt .
    [Show full text]
  • Nacldroid: Native Code Isolation for Android Applications
    NaClDroid: Native Code Isolation for Android Applications Elias Athanasopoulos1, Vasileios P. Kemerlis2, Georgios Portokalidis3, and Angelos D. Keromytis4 1 Vrije Universiteit Amsterdam, The Netherlands [email protected] 2 Brown University, Providence, RI, USA [email protected] 3 Stevens Institute of Technology, Hoboken, NJ, USA [email protected] 4 Columbia University, New York, NY, USA [email protected] Abstract. Android apps frequently incorporate third-party libraries that contain native code; this not only facilitates rapid application develop- ment and distribution, but also provides new ways to generate revenue. As a matter of fact, one in two apps in Google Play are linked with a library providing ad network services. However, linking applications with third-party code can have severe security implications: malicious libraries written in native code can exfiltrate sensitive information from a running app, or completely modify the execution runtime, since all native code is mapped inside the same address space with the execution environment, namely the Dalvik/ART VM. We propose NaClDroid, a framework that addresses these problems, while still allowing apps to include third-party code. NaClDroid prevents malicious native-code libraries from hijacking Android applications using Software Fault Isolation. More specifically, we place all native code in a Native Client sandbox that prevents uncon- strained reads, or writes, inside the process address space. NaClDroid has little overhead; for native code running inside the NaCl sandbox the slowdown is less than 10% on average. Keywords: SFI, NaCl, Android 1 Introduction Android is undoubtedly the most rapidly growing platform for mobile devices, with estimates predicting one billion Android-based smartphones shipping in 2017 [12].
    [Show full text]
  • Developing and Benchmarking Native Linux Applications on Android
    Developing and Benchmarking Native Linux Applications on Android Leonid Batyuk, Aubrey-Derrick Schmidt, Hans-Gunther Schmidt, Ahmet Camtepe, and Sahin Albayrak Technische Universit¨at Berlin, 10587 Berlin, Germany {aubrey.schmidt,leonid.batyuk,hans-gunther.schmidt,ahmet.camtepe, sahin.albayrak}@dai-labor.de http://www.dai-labor.de Abstract. Smartphones get increasingly popular where more and more smartphone platforms emerge. Special attention was gained by the open source platform Android which was presented by the Open Handset Al- liance (OHA) hosting members like Google, Motorola, and HTC. An- droid uses a Linux kernel and a stripped-down userland with a custom Java VM set on top. The resulting system joins the advantages of both environments, while third-parties are intended to develop only Java ap- plications at the moment. In this work, we present the benefit of using native applications in Android. Android includes a fully functional Linux, and using it for heavy computational tasks when developing applications can bring in substantional performance increase. We present how to develop native applications and software components, as well as how to let Linux appli- cations and components communicate with Java programs. Additionally, we present performance measurements of native and Java applications executing identical tasks. The results show that native C applications can be up to 30 times as fast as an identical algorithm running in Dalvik VM. Java applications can become a speed-up of up to 10 times if utilizing JNI. Keywords: software, performance, smartphones, android, C, Java. 1 Introduction With the growing customer interest in smartphones the number of available platforms increases steadily.
    [Show full text]
  • Java Native Interface Application Notes
    Java Native Interface Application Notes Da Ke 4/5/2009 ECE 480 Spring 2009, Design Team 3 Department of Electrical and Computer Engineering Michigan State University Abstract Java is one of most widely used programming language today due to its openness, ability to scale up and portability. The language is design to have a simpler object model and fewer low-level facilities like pointer methods in C/C++. Sometime this could impose a limitation on what a program can do. This application note will explore various ways of implementation that will allow Java to interact with some programs that are written in lower level language. Keywords: Java, JVM, JNI, Linux, Windows, Operating System, Native interface, Native code Introduction Most modern high level programming languages today are capable of handling what once consider trivial tasks for developers like memory management. However, this doesn't come without cost. A Java application does not interact with underlying system infrastructure directly instead it first compile source code to bytecode and run on Java virtual machine which itself is an application that run on top of the operating system. The Java virtual machine acts like a mediator between the application and the operating system. Most modern implementations of Java Virtual Machine does include several interfaces and libraries that we can utilize to allow Java applications to perform some system level tasks and even speed up the execution of the program by handing over some more resource-intense operations to programs that are runs natively on the machine. Objective This application note will explain different approaches to implement system level functions using Java Programming Language.
    [Show full text]
  • Calling C Library Routines from Java Using the Java Native Interface
    Numerical Algorithms Group Title: Calling C Library Routines from Java Using the Java Native Interface Summary: This paper presents a technique for calling C library routines directly from Java, saving you the trouble of rewriting code in Java and gaining portability via Java Virtual Machines. The NAG C Library from the Numerical Algorithms Group (www.nag.com) is a mathematical and statistical library containing routines for linear algebra, optimization, quadrature, differential equations, regression analysis, and time-series analysis. Although written in C, the library’s functionality can be accessed from other languages. On PCs, DLL versions of the library can be exploited in many ways, including calling from Microsoft Excel, Visual Basic, or Borland Delphi. Consequently, NAG C Library users often ask if they can call it from Java. One way to perform numerical computations is by creating Java classes that implement the required functionality. However, this is often difficult and time consuming. In this article, I present a technique for calling C Library routines directly from Java. Apart from avoiding rewriting numerical code in Java, using existing C code has another advantage. Java is portable -- compiled programs run on any machine with a Java Virtual Machine (VM). To accomplish this, the Java compiler does not compile to a machine- dependent assembler, but to machine-independent Run-Time Error Messages bytecode that is interpreted at run time by the VM. Although the interpreter is efficient, no interpreted If you get a Java error message, such as program runs as fast as programs compiled to assembler “interface library CJavaInterface cannot be code.
    [Show full text]
  • File-Based Sharing for Dynamically Compiled Code on Dalvik Virtual Machine
    File-Based Sharing For Dynamically Compiled Code On Dalvik Virtual Machine Yao-Chih Huang, Yu-Sheng Chen, Wuu Yang, Jean Jyh-Jiun Shann Department of Computer Science National Chiao Tung University Hsinchu City 300, Taiwan fychuang, yusheng, wuuyang, [email protected] Abstract—Memory footprint is considered as an impor- Generally speaking, native code that is generated by a tant design issue for embedded systems. Sharing dynamically dynamic compiler would be stored at a memory area called compiled code among virtual machines can reduce memory code cache. In the Android platform, every virtual machine footprint and recompilation overhead. On the other hand, sharing writable native code may cause security problems, would allocate its own code cache. Thus, native code might due to support of native function call such as Java Native be duplicated in several code cache and result in wasting Interface (JNI). We propose a native-code sharing mechanism of memory. On the other hand, same native code may be that ensures the security for Dalvik virtual machine (VM) on compiled repeatedly and result in reduced performance. the Android platform. Dynamically generated code is saved in So, sharing native code in the code cache among virtual a file and is shared with memory mapping when other VMs need the same code. Protection is granted by controlling of file machines can reduce memory footprint. This sharing ap- writing permissions. To improve the security, we implement a proach also avoids repeated compilation of the same code daemon process, named Query Agent, to control all accesses and hence improve performance. to the native code and maintain all the information of traces, There exist two works about code sharing in VM : which are the units of the compilation in the Dalvik VM.
    [Show full text]
  • Box2d with Libgdx
    [ 1 ] www.allitebooks.com LibGDX Game Development By Example Learn how to create your very own game using the LibGDX cross-platform framework James Cook BIRMINGHAM - MUMBAI www.allitebooks.com LibGDX Game Development By Example Copyright © 2015 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: August 2015 Production reference: 1210815 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78528-144-0 www.packtpub.com www.allitebooks.com Credits Author Project Coordinator James Cook Mary Alex Reviewers Proofreader Pavel Czempin Safis Editing Lévêque Michel Sudarshan Shetty Indexer Monica Ajmera Mehta Acquisition Editors Subho Gupta Graphics Dan Smallman James Jones Jason Monteiro Content Development Editor Nikhil Potdukhe Production Coordinator Arvindkumar Gupta Technical Editor Abhishek R.
    [Show full text]
  • Including Native Methods in Static Analysis of Java Programs by Victor L
    Including Native Methods in Static Analysis of Java Programs by Victor L. Hernandez Submitted to the Department of Electrical Engineering and Computer Science in partial fulfillment of the requirements for the degree of Master of Engineering in Electrical Engineering and Computer Science at the MASSACHUSETTS INSTITUTE OF TECHNOLOGY June 2000 @ Massachusetts Institute of Technology 2000. All rights reserved. A uthor ........................... .... Department of Electrical Engineering and Computer Science May 22, 2000 Certified by ....................... K' hris Terman Senior Lecturer Massachusetts Institute of Technology Thesis Supervisor Accepted by ................ .. .-... 4.. Arthur C. Smith Chairman, Department Committee on Graduate Students MASSACHUSETS IST OF TECHNOLOGY ur JUL 2 7 2000 LIBRARIES Including Native Methods in Static Analysis of Java Programs by Victor L. Hernandez Submitted to the Department of Electrical Engineering and Computer Science on May 22, 2000, in partial fulfillment of the requirements for the degree of Master of Engineering in Electrical Engineering and Computer Science Abstract Most static analyses of Java programs treat native methods conservatively due the analy- ses' dependence on bytecodes or source code for the syntactic and semantic analysis of the method bodies. This thesis presents a less-conservative approach that extracts sufficient information from native methods and transforms them into a representation that facilitates their inclusion in the analysis of Java programs. The approach focuses on analyses of Java programs that are concerned with the propagation of Java object references, such as escape analysis and mutability analysis. The Java Native Interface has become the standard for including C/C++ source in Java applications. With object reference propagation being the focus, the task of extracting information from native methods becomes that of separating the Java semantics associated with calls to the Java Native Interface (JNI) from the semantics of the remainder of the C/C++ code.
    [Show full text]
  • C and C++ JNI and STL
    JNI and STL C and C++ This lecture looks at: 8. JNI and STL I Java Native Interface (JNI) as an example of the sort of techiques you need for mixed language working. C (rather than C++) is often used because of it being a “high-level assembly language”. Alan Mycroft I The Standard Template Library for C++. University of Cambridge (heavily based on previous years’ notes – thanks to Alastair Beresford and Andrew Moore) The treatment is more of an overview compared to the previous lectures (i.e. you only have to understand the large-scale issues in inter-language Michaelmas Term 2013–2014 working and the STL, rather than needing to learn all the details). 1 / 41 2 / 41 JNI — Java Native Interface Justification Java Native Interface (JNI) is the Java interface to non-Java code. I interoperate with applications and libraries written in other programming languages (e.g., C, C++, assembly) Pro: I Reuse: allow access to useful native code Examples we will look at: I Efficiency: use best language for the right task I Embedding C in Java I Using Java from C Cons: Why use JNI? I Applets: mobility makes this painful I Portability: native methods aren’t portable I Low-level specifics not provided by Java I Extra work: javah, creating shared library I Performance (java is not famous for being fast) I Legacy code wrapper 3 / 41 4 / 41 Embedding C in Java Generate JNI Header 1. Declare the method using the keyword native (without implementation) 2. (Make sure Java loads the required library) 3.
    [Show full text]
  • Identifying Java Calls in Native Code Via Binary Scanning
    Identifying Java Calls in Native Code via Binary Scanning George Fourtounis Leonidas Triantafyllou Yannis Smaragdakis University of Athens University of Athens University of Athens Athens, Greece Athens, Greece Athens, Greece [email protected] [email protected] [email protected] ABSTRACT An often-overlooked fact, however, is that platform-specific (na- Current Java static analyzers, operating either on the source or byte- tive) code is far from absent in the Java world. Advanced appli- code level, exhibit unsoundness for programs that contain native cations often complement their platform-independent, pure-Java code. We show that the Java Native Interface (JNI) specification, functionality with specialized, platform-specific libraries. In An- which is used by Java programs to interoperate with Java code, droid, for instance, Almanee et al. [1] find that 540 of the 600 top is principled enough to permit static reasoning about the effects free apps in the Google Play Store contain native libraries, at an of native code on program execution when it comes to call-backs. average of 8 libraries per app! (The architectural near-monopoly of Our approach consists of disassembling native binaries, recovering ARM in Android devices certainly does nothing to discourage the static symbol information that corresponds to Java method signa- trend.) Desktop and enterprise Java applications seem to use native tures, and producing a model for statically exercising these native code much more sparingly, but native code still creeps in. Popular call-backs with appropriate mock objects. projects such as log4j, lucene, aspectj, or tomcat use native code for The approach manages to recover virtually all Java calls in native low-level resource access [11].
    [Show full text]