DOCSLIB.ORG

Development of Responsive Multi-Device Applications Within Apple Ecosystem

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Development of Responsive Multi-Device Applications Within Apple Ecosystem Development of Responsive Multi-Device Applications within Apple Ecosystem Jingkai He Supervisor: Dr Charaka Palansuriya August 14, 2014 Contents Acknowledgement ....................................................................................................... 1 Abbreviations ............................................................................................................... 2 Abstract ........................................................................................................................ 3 1 Introduction and Objectives ................................................................................... 4 2 Background and Literature Review ....................................................................... 6 2.1 State of The Art of Multi-Device Application Development ............................ 6 2.2 Background Knowledge of Apple Ecosystem ................................................... 7 2.2.1 Memory Management ................................................................................. 8 2.2.2 User interface .............................................................................................. 8 2.2.3 Data Model ................................................................................................. 8 2.3 HPC in Multi-Device Application Development .............................................. 8 2.3.1 Clang Compiler ........................................................................................... 9 2.3.2 Grand Central Dispatch ............................................................................ 10 3 Functional Specification and Design ................................................................... 11 3.1 Functional Specification .................................................................................. 11 3.1.1 Basic Functionality ................................................................................... 11 3.1.2 Advanced Functionality ............................................................................ 12 3.2 Architecture ..................................................................................................... 13 3.3 Design .............................................................................................................. 14 3.4 Library Design ................................................................................................. 14 3.5 User Interface Design ...................................................................................... 15 3.5.1 iOS Human Interface Guidelines .............................................................. 15 3.5.2 Mac OS X Human Interface Guidelines ................................................... 16 3.5.3 User Interface for iOS Device .................................................................. 17 3.5.4 User Interface for OS X Device ................................................................ 17 3.5.5 Application Layout ................................................................................... 18 i 3.6 Model Layer Design ........................................................................................ 19 4 Implementation .................................................................................................... 20 4.1 Some Hardware and Software used in the Project ........................................... 20 4.2 Library Implementation ................................................................................... 20 4.2.1 Section and Subsection ............................................................................. 21 4.2.2 Paragraph .................................................................................................. 22 4.2.3 Horizontal Line ......................................................................................... 22 4.2.4 Rich Text among Paragraphs .................................................................... 22 4.2.5 List ............................................................................................................ 24 4.3 Application Implementation ............................................................................ 24 4.3.1 Common Model Layer .............................................................................. 24 4.3.2 iOS Controller Layer Development .......................................................... 25 4.3.3 OS X Controller Layer Development ....................................................... 26 4.4 Design Pattern .................................................................................................. 27 4.4.1 Delegation Pattern .................................................................................... 27 4.4.2 Active Record Pattern ............................................................................... 28 4.4.3 Monkey Patching ...................................................................................... 28 4.4.4 Observer Pattern ....................................................................................... 29 5 Performance Optimisation ................................................................................... 30 5.1 Profiling Approaches ....................................................................................... 30 5.1.1 Hardware for Profiling .............................................................................. 31 6 Result and Evaluation .......................................................................................... 32 6.1 Application Run on OS X device .................................................................... 32 6.2 Application Run on iOS device ....................................................................... 33 6.3 Markdown Parser Optimisation ....................................................................... 35 6.3.1 Object Loading Optimisation ................................................................... 35 6.3.2 Multithreading Optimisation .................................................................... 40 6.3.3 Multithreading Overhead Reducing ......................................................... 44 ii 6.4 Optimisation on OS X Platform ...................................................................... 48 6.4.1 Reduce Unnecessary View Rendering ...................................................... 48 6.4.2 Asynchronous Non-blocking Rendering .................................................. 51 6.5 Optimisation on iOS Platform ......................................................................... 52 6.5.1 Multithreading Optimisation .................................................................... 52 6.5.2 Table View Optimisation .......................................................................... 54 7 Conclusions and Future Work ............................................................................. 56 7.1 Future Work ..................................................................................................... 56 References .................................................................................................................. 58 iii Acknowledgement I would like to express my great appreciation to my supervisor, Dr Charaka Palansuriya, for his generous and thoughtful suggestions and guidance all through the dissertation. I would also like to thank EPCC for providing me with great teaching resource and opportunity to work on the world-class computation hardware during the MSc study. Finally, I would like to thank my parents, for their support and encouragement throughout my study. 1 Abbreviations ARC Automatic Reference Counting GCD Grand Central Dispatch GUI Graphical User Interface SDK Software Development Kit UI User Interface VM Virtual Machine 2 Abstract Mobile devices, such as laptops, tablets and smartphones are increasingly being used in daily work. A successful application is expected to be available on many such devices. The project explores the state-of-the-art in developing multi-device applications with high responsiveness within Apple ecosystem. To identify the methodology suitable for such multi-device development, a notebook application using Markdown syntax is developed on Apple devices. It is implemented to be compatible for devices with different screen size and take the advantage of device-specific hardware. After the notebook application is developed, some high performance related technologies and tools are applied to optimise the performance and improve the responsiveness of the application. The techniques used include enable the application to run on multi-cores by using multithreading, reducing the CPU and memory usage by lazy loading objects and applying caching technology. The responsiveness of the application before and after the performance optimisation is then discussed. 3 1 Introduction and Objectives Presently laptops, smart phones and tablets are one the most popular computing devices used by people. The markers of the operating systems running on those devices usually provide developer with Software Development Kits (to be called SDK for short) so that developers can build applications within the chosen software ecosystem. This can create a win-win situation: As developer can be profitable by making popular software, platform will also be popular due to quantity and quality of the software available on it. A large number of successful applications nowadays are now built for different devices and running on different operating systems. One example is the Microsoft Office, which is built on Windows,
Load more

Recommended publications
  • Developing with Pojos: Faster and Easier 3 Chapter 2 ■ J2EE Design Decisions 31
    FROM OUR PEER REVIEW ... “Chris Richardson targets critical design issues for lightweight Java enterprise applications using POJOs with fantastic in-depth exam- ples. This book extends Martin Fowler’s great book, Enterprise Architecture Patterns, as well as the more recent Domain-Driven Design by Eric Evans, by providing practical design guidance and useful examples. It also addresses the architecture and design issues asso- ciated with Spring and Hibernate development, whereas Man- ning’s companion ‘in Action’ books focus primarily on the Spring and Hibernate technologies. “This is a powerful book for architects, senior developers, and consultants. It uniquely combines best practices and design wisdom to integrate domain-driven design and test-driven development for object-oriented Java enterprise applications using lightweight Spring, Hibernate, and JDO technologies. “The table of contents reflects the important topics that most architects and enterprise developers face every day. There is signifi- cant need for a book like this, which shows how to address many common and complex design issues with real-world examples. The content in this book is unique and not really available elsewhere.” DOUG WARREN Software Architect Countrywide Financial “POJOs in Action fills a void: the need for a practical explanation of the techniques used at various levels for the successful building of J2EE projects. This book can be compared with the less enterprise- oriented and more abstract J2EE Development without EJB by Rod Johnson, but Richardson offers a step-by-step guide to a successful J2EE project. The explanations of the various alternatives available for each step provide the main thrust of this book.
    [Show full text]
  • Object Oriented Paradigm/Programming
    an object is an instantiation from a class, e.g., you have a pet cat, who's Object Oriented Paradigm name is Garfield, then Garfield is a object (of the class cat) to invoke an method, simply do obj.method( ) or obj->method( ), the Ming- Hwa Wang, Ph.D. former is object reference syntax, and the latter is pointer syntax Department of Computer Engineering Santa Clara University Relationships a-kind-of relationship: a subclass inherits and adds more attributes Object Oriented Paradigm/Programming (OOP) and/or methods from its super class to become somewhat "specialized" similar to Lego, which kids build new toys from assembling the existing is-a relationship: an object of a subclass is an object of its super class construction blocks of different shapes part-of relationship: OOP - doing programs by reusing (composing/inheriting) objects has-a relationship: (instantiated from classes) as much as possible, and only writing code when no exiting objects can be applied Reusability inheritance Two Fundamental Principles for OOP a sub/child/derived/extended class can inherit all properties from its generalization or reusability: the classes designed should target to super/parent/base/original class, with or without reusability, i.e., it should very generic and can be applied to lots of modification/override or addition situations/applications without much efforts; reusability comes from single inheritance and multiple inheritance (watch out naming inheritance and/or composition conflicts) encapsulation or information hiding: we can hide detailed or composition implementation specific information away from the users/programmers, so changing implementation using the same interfaces will not need Abstract or Virtual Classes modifying the application code only used as a super class for other classes, only specified but not fully defined, and can't be instantiated OOP Language vs.
    [Show full text]
  • [ Team Lib ] Crawford and Kaplan's J2EE Design Patterns Approaches
    [ Team LiB ] • Table of Contents • Index • Reviews • Reader Reviews • Errata J2EE Design Patterns By William Crawford, Jonathan Kaplan Publisher: O'Reilly Pub Date: September 2003 ISBN: 0-596-00427-3 Pages: 368 Crawford and Kaplan's J2EE Design Patterns approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software. They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability. [ Team LiB ] [ Team LiB ] • Table of Contents • Index • Reviews • Reader Reviews • Errata J2EE Design Patterns By William Crawford, Jonathan Kaplan Publisher: O'Reilly Pub Date: September 2003 ISBN: 0-596-00427-3 Pages: 368 Copyright Preface Audience Organization of This Book For Further Reading Conventions Used in This Book Comments and Questions Acknowledgments Chapter 1. Java Enterprise Design Section 1.1. Design Patterns Section 1.2. J2EE Section 1.3. Application Tiers Section 1.4. Core Development Concepts Section 1.5. Looking Ahead Chapter 2. The Unified Modeling Language Section 2.1. Origins of UML Section 2.2. The Magnificent Seven Section 2.3. UML and Software Development Lifecycles Section 2.4. Use Case Diagrams Section 2.5. Class Diagrams Section 2.6. Interaction Diagrams Section 2.7.
    [Show full text]
  • Critical Resource Concurrency Pattern in C++
    ApriorIT Inc. Implementation of Critical Resource Concurrency Pattern in C++ Implementation of Critical Resource Concurrency Pattern in C++ The article is written by Vladimir Frolov, system developer of ApriorIT. The topic area of concurrency patterns is poorly covered in literature, so this text is called to fill a gap, at least partly. Many of those who have ever used Critical Section object for synchronization between threads were applying it together with Auto Critical Section object. Indeed, Auto Critical Section is a powerful synchronization object which use has a set of advantages. The code containing Auto Critical Section for Critical Section management turns safe, more readable and structured when compared with the code directly working with Critical Section. Moreover, Auto Critical Section has trivial implementation. Regarding Auto Critical Section object one might say that it wraps in Critical Section the scope in which it is being created. However, whether Auto Critical Section used or not, there is still a series of problems relating to Critical Section object: • the Critical Section and resource which it protects are being created separately and can potentially have different lifetime. • the code which uses the resource must know that access to it is synchronized by critical section. Both these problems are of little importance if the critical section is used for creation of a thread- safe class. In that case the critical section is being created as data member and about it should be aware only function members of the given class while creating an Auto Critical Section object on call. However, a problem appears if it is necessary to provide access to a resource or class object which doesn't make any attempts at synchronization from within.
    [Show full text]
  • Interacting with *OS Hardware from User Space
    Interacting with *OS Hardware from User Space ??? Jiska Classen Secure Mobile Networking Lab - SEEMOO Technical University of Darmstadt, Germany As a… hardware hacker I want to… buy iPhones So that… I can break the most recent chips Wait, what? ● Official development kits often lag behind. ○ Bluetooth/Wi-Fi kits by Cypress (aka Broadcom) are stuck on a firmware state around 2016. ○ Ultra Wideband kits by Decawave added features like direction measurement much later than it was available in iPhones. ● Official development kits miss proprietary features. ○ Intel baseband chips use a proprietary, undocumented interface on Apple devices. Bluetooth Chip Build Dates iPhone 11: Oct 25 2018 iPhone 12: Oct 29 2019 Samsung Galaxy S21: April 13 2018 (S21+ Ultra probably got an update) Hardware in an iPhone ● Bluetooth+Wi-Fi combo chip by Broadcom ● Baseband chip by Intel or Qualcomm ● U1 chip (in-house, since iPhone 11) ● NFC chip ● … and that’s just the wireless chips! If I deal with iPhones, jailbreaks, etc. I can access quite a lot of hardware Goals 1. Find chip interfaces. 2. Find protocol handlers. 3. Decode proprietary protocols. 4. Inject custom payloads. ??? Why from user space?! ● The daemon that interacts with the chip already holds a correct state. ○ Chip initialization/activation on startup and when leaving flight mode. ○ Complex protocol internals are implemented here. ● The daemon’s protocol implementation will typically: ○ parse crash logs, ○ acknowledge packets, CommCenter ○ forward information to other daemons, ○ … User Space Kernel Space ● FЯIDA only supports user space. Hardware But you said *OS??! ● XNU kernel is very similar on MacOS, iOS, and the iOS derivatives like audioOS, watchOS, tvOS, … ● User space is also mostly similar.
    [Show full text]
  • 60 Years of Mastering Concurrent Computing Through Sequential Thinking Sergio Rajsbaum, Michel Raynal
    60 Years of Mastering Concurrent Computing through Sequential Thinking Sergio Rajsbaum, Michel Raynal To cite this version: Sergio Rajsbaum, Michel Raynal. 60 Years of Mastering Concurrent Computing through Sequential Thinking. ACM SIGACT News, Association for Computing Machinery (ACM), 2020, 51 (2), pp.59-88. 10.1145/3406678.3406690. hal-03162635 HAL Id: hal-03162635 https://hal.archives-ouvertes.fr/hal-03162635 Submitted on 17 Jun 2021 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. 60 Years of Mastering Concurrent Computing through Sequential Thinking ∗ Sergio Rajsbaumy, Michel Raynal?;◦ yInstituto de Matemáticas, UNAM, Mexico ?Univ Rennes IRISA, 35042 Rennes, France ◦Department of Computing, Hong Kong Polytechnic University [email protected] [email protected] Abstract Modern computing systems are highly concurrent. Threads run concurrently in shared-memory multi-core systems, and programs run in different servers communicating by sending messages to each other. Concurrent programming is hard because it requires to cope with many possible, unpre- dictable behaviors of the processes, and the communication media. The article argues that right from the start in 1960’s, the main way of dealing with concurrency has been by reduction to sequential reasoning.
    [Show full text]
  • Mac OS X Desktop.Pdf
    Apple Training Series Mac OS X Support Essentials v10.6 Kevin M. White Apple Training Series: Mac OS X Support Essentials v10.6 Kevin M. White Copyright © 2010 by Apple Inc. Published by Peachpit Press. For information on Peachpit Press books, contact: Peachpit Press 1249 Eighth Street Berkeley, CA 94710 510/524-2178 510/524-2221 (fax) www.peachpit.com To report errors, please send a note to [email protected]. Peachpit Press is a division of Pearson Education. Apple Training Series Editor: Rebecca Freed Production Editors: Danielle Foster, Becky Winter Copyeditor: Peggy Nauts Tech Editor: Gordon Davisson Apple Editor: Shane Ross Proofreader: Suzie Nasol Compositor: Danielle Foster Indexer: Valerie Perry Cover design: Mimi Heft Cover illustrator: Kent Oberheu Notice of Rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For infor- mation on getting permission for reprints and excerpts, contact [email protected]. Notice of Liability The information in this book is distributed on an “As Is” basis without warranty. While every precaution has been taken in the preparation of the book, neither the author nor Peachpit shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the computer software and hardware products described in it. Trademarks Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
    [Show full text]
  • Session 6 Software Design Patterns
    I402A Software Architecture and Quality Assessment Session 6 Software Design Patterns Sébastien Combéfis Fall 2019 This work is licensed under a Creative Commons Attribution – NonCommercial – NoDerivatives 4.0 International License. Objectives Implementation pattern and excellence in programming Communication, simplicity and flexibility Other categories of software design patterns Concurrency patterns for synchronisation, communication, etc. Architectural patterns in relation with enterprise solutions Green patterns for sustainable development 3 Implementation Pattern Implementation Pattern One should aim for excellence in programming Best program offerts best extension option, has no unrelated elements and is easy to understand Three values that are important to strive to excellence Communication: read can understand, modify and use Simplicity: no unnecessary complexity for the program Flexibility: allows for easy evolution and changes 5 Principle (1) Structure the code to ensure local consequences A change “here” can not result in a problem “there” Minimise repetitions of code, structure, algorithm, etc. Duplication, parallel class hierarchies, similar code Keep together data and the logic manipulating them Following the object oriented programming paradigm 6 Principle (2) Make explicit symmetry at different levels The presence of an add should suggest a remove Express intentions as declaratively as possible Use annotations in imperative programming Gather code and data by change rate Allows changes to the same place at the same time 7
    [Show full text]
  • Grand Central Dispatch
    Grand Central Dispatch Marcio Rocha dos Santos Trabalho de conclusão de curso Orientador: Prof. Dr. Alfredo Goldman vel Lejbman Co-Orientador: Emilio De Camargo Francesquini São Paulo, Dezembro de 2010 Sumário 1 Introdução1 2 História 3 3 Conceitos 5 3.1 Programação paralela................................5 3.2 Speedup e eficiência.................................6 3.3 Programação concorrente..............................7 4 Grand Cental Dispatch9 4.1 Block Objects.................................... 10 4.1.1 Sintaxe.................................... 11 4.2 Dispatch queues................................... 11 4.3 Synchronization................................... 12 4.4 Event sources.................................... 13 5 Atividades realizadas 15 5.1 Explorando as funcionalidades........................... 15 5.2 Testes de desempenho e Resultados obtidos.................... 16 iv SUMÁRIO 5.2.1 Tarefas crescentes.............................. 16 5.2.2 Tarefas curtas................................ 17 5.2.3 Divisão do trabalho............................. 18 6 Conclusões 19 Capítulo 1 Introdução No passado, o melhor caminho para os fabricantes de chips melhorarem o desempenho dos computadores, foi o de aumentar a velocidade do clock do processador. Mas não demorou muito a esbarrar num conjunto de limitantes físicos. um desses limitantes é a chamada power wall ou "barreira de potência", que ocorre devido ao alto tráfego de energia através dos chips, e a perda dessa energia na forma de calor pode até fazer com que o chip alcance a temperatura de fusão do metal que o compõe, arruinando-o completamente. Os sistemas atuais de arrefecimento já estão com certa dificuldade de dissipar esse calor de um modo eficiente e barato. Entretanto, como a demanda por computadores de alto desempenho continua crescendo, a indústria mudou para chips com múltiplos núcleos e clocks menores, que pode fornecer mais desempenho, consumindo menos energia.
    [Show full text]
  • Grand Central Dispatch
    Mastering Grand Central Dispatch Session 210 Daniel Steffen Core OS These are confidential sessions—please refrain from streaming, blogging, or taking pictures 1 Grand Central Dispatch • Introduced in Mac OS X Snow Leopard and iOS 4 • Core technology for asynchrony and concurrency • Identical API and functionality across platforms and hardware 2 Grand Central Dispatch Overview • Brief introduction to GCD • What is new in GCD on Mac OS X Lion and iOS 5 • Advanced usage of GCD API 3 Introduction to GCD Blocks and Queues 4 Blocks Encapsulate units of work id obj = [Example new]; int arg = 5; later( ^{ !! [obj doSomething:arg]; }); arg = 6; [obj doSomething:arg]; [obj release]; 5 Queues Serialization • Lightweight list of blocks • Enqueue and dequeue are FIFO • Serial queues execute blocks one at a time 6 Queues Concurrency • Concurrent queues execute multiple blocks at the same time • Concurrently executed blocks may complete out of order • Queues execute concurrently with respect to other queues 7 Serial Queues 5 ^{ … } ^{ … } ^{ … } ^{ … } ^{ … } Time 8 Concurrent Queue ^{ … } ^{ … } ^{ … } ^{ … } ^{ … } Time 9 Queues API • Submitting blocks to queues dispatch_async(queue,dispatch_async ^{ /* Block */ }); dispatch_sync(queue,dispatch_sync ^{ /* Block */ }); • Submitting blocks later dispatch_afterdispatch_after(when, queue, ^{ /* Block */ }); • Concurrently executing one block many times dispatch_applydispatch_apply(iterations, queue, ^(size_t i){ /* Block */ }); 10 Queues API • Suspending and resuming execution dispatch_suspend(queue);dispatch_suspend
    [Show full text]
  • 706 Modernizing Grand Central
    System Frameworks #WWDC17 Modernizing• GCD Usage • How to stay on core • Session 706 Daniel Chimene, Core Darwin Daniel A. Steffen, Core Darwin Pierre Habouzit, Core Darwin © 2017 Apple Inc. All rights reserved. Redistribution or public display not permitted without written permission from Apple. dispatch_async dispatch_queue_create DispatchQueue.concurrentPerform dispatch_after DispatchQueue.async dispatch_sync DispatchQueue.sync dispatch_activate DispatchSource.activate dispatch_source_create DispatchSource.setEventHandler dispatch_once dispatch_apply DispatchWorkItem.notify A4 A5 A6 A7 A8 A9 A10 Efficiency Through Observation Going off core during an operation reduces efficiency Efficiency 10µs 500µs 1ms Observation Time 1.3x faster after combining queue hierarchies • Parallelism and concurrency • Parallelism and concurrency • Using GCD for concurrency • Parallelism and concurrency • Using GCD for concurrency • Unified Queue Identity • Parallelism and concurrency • Using GCD for concurrency • Unified Queue Identity • Finding problem spots Parallelism Simultaneous execution of closely related computations Concurrency Composition of independently executed tasks Parallelism• Parallelism Simultaneous execution of closely related computations Parallelism Simultaneous execution of closely related computations Parallelism Simultaneous execution of closely related computations Take Advantage of System Frameworks Accelerate Metal 2 Core ML Core Animation Parallelism with GCD Express explicit parallelism with DispatchQueue.concurrentPerform Parallel
    [Show full text]
  • POJO in Action.Book
    SAMPLE CHAPTER POJOs in Action by Chris Richardson Chapter 2 Copyright 2006 Chris Richardson contents PART 1OVERVIEW OF POJOS AND LIGHTWEIGHT FFFFFFFFFFFFFFFFRAMEWORKS .............................................1 Chapter 1 ■ Developing with POJOs: faster and easier 3 Chapter 2 ■ J2EE design decisions 31 PART 2A SIMPLER, FASTER APPROACH................... 59 Chapter 3 ■ Using the Domain Model pattern 61 Chapter 4 ■ Overview of persisting a domain model 95 Chapter 5 ■ Persisting a domain model with JDO 2.0 149 Chapter 6 ■ Persisting a domain model with Hibernate 3 195 Chapter 7 ■ Encapsulating the business logic with a POJO façade 243 PART 3VARIATIONS ........................................... 287 Chapter 8 ■ Using an exposed domain model 289 Chapter 9 ■ Using the Transaction Script pattern 317 Chapter 10 ■ Implementing POJOs with EJB 3 360 vii viii BRIEF CONTENTS PART 4DEALING WITH DATABASES AND CCCCCCCCCCCCCONCURRENCY .......................................405 Chapter 11 ■ Implementing dynamic paged queries 407 Chapter 12 ■ Database transactions and concurrency 451 Chapter 13 ■ Using offline locking patterns 488 J2EE design decisions This chapter covers ■ Encapsulating the business logic ■ Organizing the business logic ■ Accessing the database ■ Handling database concurrency 31 32 CHAPTER 2 J2EE design decisions Now that you have had a glimpse of how POJOs and lightweight frameworks such as Spring and JDO make development easier and faster, let’s take a step back and look at how you would decide whether and how to use them. If we blindly used POJOs and lightweight frameworks, we would be repeating the mistake the enter- prise Java community made with EJBs. Every technology has both strengths and weaknesses, and it’s important to know how to choose the most appropriate one for a given situation.
    [Show full text]