Technologies for Web and Cloud Service Interaction: a Survey

Total Page:16

File Type:pdf, Size:1020Kb

Technologies for Web and Cloud Service Interaction: a Survey Service Oriented Computing and Applications manuscript No. (will be inserted by the editor) Technologies for Web and cloud service interaction: a survey Harald Lampesberger Received: date / Accepted: date Abstract The evolution of Web and service technologies 1 Introduction has led to a wide landscape of standards and protocols for interaction between loosely coupled software components. The need to share network-based resources and use remote Examples range from Web applications, mashups, apps, and functionality in a program without dealing with low-level mobile devices to enterprise-grade services. Cloud comput- network access has fueled discussions in the 1970s [263, ing is the industrialization of service provision and deliv- 290,369] and ultimately led to the remote procedure call ery, where Web and enterprise services are converging on (RPC) framework by Birrell and Nelson [37] in the 1980s. a technological level. The article discusses this technologi- RPC became a driver in enterprise systems; location trans- cal landscape and, in particular, current trends with respect parency of procedures eases code reuse but requires tight to cloud computing. The survey focuses on the communi- coupling, e.g., a unified type system. In the 1990s, the prin- cation aspect of interaction by reviewing languages, proto- ciples of object orientation and RPC gave raise to distributed cols, and architectures that drive today’s standards and soft- objects [222]. Tight coupling and interaction complexity in ware implementations applicable in clouds. Technological RPC and distributed objects affected the scalability of enter- advances will affect both client side and service side. There prise systems, and at the end of the 1990s, message passing is a trend toward multiplexing, multihoming, and encryption between so-called services became an alternative enterprise in upcoming transport mechanisms, especially for architec- architecture with relaxed coupling and easier scalability. To- tures, where a client simultaneously sends a large number of day, middleware for message queuing and the concept of requests to some service. Furthermore, there are emerging service-oriented architecture (SOA) [212] dominate large- client-to-client communication capabilities in Web clients scale distributed enterprise systems. that could establish a foundation for upcoming Web-based messaging architectures. In the meantime, Berners-Lee [360] laid out the foun- dation for a World Wide Web of nonlinear text documents, i.e., hypertext, exchanged in a client-server architecture over Keywords Web technology · Web services · Cloud arXiv:1408.2751v3 [cs.NI] 9 Mar 2015 the predecessor of today’s Internet in 1989. The first Web services · Service architecture · Communication protocols · browser was announced end of 1990, the World Wide Web Languages · Service interaction patterns Consortium (W3C) was established in 1994, and W3C pub- lished the first Hypertext Markup Language (HTML) Rec- ommendation in 1997. Since then, the Web has evolved from H. Lampesberger Christian Doppler Laboratory for Client-Centric Cloud Computing, simple hypermedia exchange, to interactive user interfaces, Johannes Kepler University Linz, rich client applications, user-provided content, mashups, so- Softwarepark 21, 4232 Hagenberg, Austria cial platforms, and wide-scale mobile device support. Web E-mail: [email protected] technology has become pervasive and is not limited to hy- This is the author’s accepted draft. Please cite the published ver- permedia applications anymore. Standards are widely ac- sion: Lampesberger, H.: Technologies for Web and cloud service cepted, and they have contributed to the success of Web ser- interaction: a survey. Service Oriented Computing and Applications vices because protocols like the Hypertext Transfer Protocol (2015). DOI 10.1007/s11761-015-0174-1 (HTTP) are reliably forwarded over the Internet [4,253]. 2 Harald Lampesberger Cloud computing [24] can be seen as the industrializa- Service Interaction Pattern Section3 tion of service provision and delivery over the Internet using established technologies from the Web [90] and from en- terprise services [35]. The goal is to offer a service, acces- Protocol Architecture sible across devices, systems, and platforms. Interaction by communication between service consumers and providers, Language Implementation i.e., clients and services, is therefore a key aspect of service Section4 Section2 Section5 delivery. Cloud service delivery models like Platform-as-a- Service (PaaS) or Software-as-a-Service (SaaS) benefit from well-known Web standards and their wide acceptance [24, Fig. 1 The concepts and their relationships found in communication technologies also reflect in the structure of the survey 90,292]. To acknowledge this relation between Web and ser- vices technology, this article surveys the state-of-the-art and recent trends in technologies applicable in clouds. munication technologies applicable to the Web, PaaS, and SaaS are surveyed. 1.1 Scope 1.2 Motivation A survey of technologies in such a dynamic environment needs a defined scope. All technologies that allow a client This survey is motivated by ongoing research efforts in for- to interact with a service should be considered; however, the mal modeling of cloud services [48,44,292], modeling of notion of service is not precisely defined [292]. The follow- service quality [269,268], service adaptation [56], identity ing informal properties and restrictions therefore character- management [326,325], and security monitoring [159,158, ize a service in context of this work: 160] for cloud services. All these aspects need communica- tion between clients and services. Understanding the state- – Service interface. Services are considered as distributed, of-the-art in service communication is therefore necessary, network-accessible software components that offer func- e.g., for security research because an ambiguous or impre- tionality and need communication for interaction [107, cise service interface is in fact a gateway for attacks [288]. 253]. A notion of interface that accepts a certain lan- There is a rich body of literature using patterns to de- guage is therefore required. The survey is restricted to scribe service interaction on a conceptual level [1,26,25, technologies that enable communication between clients 118,378]. On the other hand, the numerous software imple- and service interfaces applicable in Web, PaaS, and SaaS mentations used in today’s services are heavily driven by cloud delivery models. continuously evolving standards and ad hoc specifications. – Heterogeneous platforms. A characteristic of service- This work aims to bridge this gap by surveying the state-of- orientation is to provide functionality and content across the-art of technologies and resort to patterns when concepts hard- and software platforms. Only technologies that em- are discussed. Patterns are appealing because they allow to brace this compatibility are considered. describe solutions in a conceptual way and can therefore – Publicly available standards. The focus is on technolo- support service integrators and scientists in understanding gies that are available to the public audience, in partic- new technologies. ular, technologies based on Internet protocols, i.e., the TCP/IP protocol suite [302], and with publicly available specifications. Specialized technologies for a limited au- 1.3 Methodology and structure dience or application, like industrial control systems, are not part of this study. The problem is approached both in top-down and bottom- – Parties. There are two participating parties or peers in up manners. In the top-down view, entities of information service interaction: a client that consumes some service are exchanged between peers, i.e., clients and services, in an offered by a provider or server, i.e., client-to-service in- agreed-upon style, i.e., interaction pattern. The article there- teraction. On a conceptual level, a service can participate fore discusses languages for encapsulation information, so also as a client to consume other services for a compo- information becomes transportable. The bottom-up view in- sition, i.e., service-to-service interaction. Furthermore, a vestigates how an agreed-upon style of interaction is actu- service can coordinate two clients to establish client-to- ally implemented in today’s networks, i.e., communication client or peer-to-peer interaction. protocols and architectures for information exchange. Fig. 1 visualizes the relationships between concepts required for In accordance with the aforementioned characteristics, service interaction. The relations and concepts have been de- the state-of-the-art and recent trends in Web and service com- rived from the extensive literature review in this article. Technologies for Web and cloud service interaction: a survey 3 Languages are fundamental for communication. A lan- by nonprofit organizations, communities, consortia but also guage defines an alphabet, syntax, and semantics to repre- enterprises. Important institutions are therefore recalled. sent information in a transportable format. Languages there- To develop industrial standards on a global scale such fore encode content, media, and information in general. Pop- as specifications for electronic communication devices, e.g., ular languages in the Web and for services are discussed in networking, the International Organization for Standardiza- Sect.2. tion (ISO) [132], the International Electrotechnical Com- Due to
Recommended publications
  • AJAX Requests CPEN400A - Building Modern Web Applications - Winter 2018-1
    What is AJAX XmlHttpRequest Callbacks and Error Handling JSON Lecture 6: AJAX Requests CPEN400A - Building Modern Web Applications - Winter 2018-1 Karthik Pattabiraman The Univerity of British Columbia Department of Electrical and Computer Engineering Vancouver, Canada Thursday, October 17, 2019 What is AJAX XmlHttpRequest Callbacks and Error Handling JSON What is AJAX ? 2 1 What is AJAX 2 XmlHttpRequest 3 Callbacks and Error Handling 4 JSON What is AJAX XmlHttpRequest Callbacks and Error Handling JSON What is AJAX ? 3 Mechanism for modern web applications to communicate with the server after page load Without refreshing the current page Request can be sent asynchronously without holding up the main JavaScript thread Stands for “Asynchronous JavaScript and XML”, but does not necessarily involve XML Complement of COMET (Server Push) What is AJAX XmlHttpRequest Callbacks and Error Handling JSON A Brief History of AJAX 4 Introduced by Microsoft as part of the Outlook Web Access (OWA) in 1998 Popularized by Google in Gmail, Maps in 2004-05 Term AJAX coined around 2005 in an article Made part of the W3C standard in 2006 Supported by all major browsers today What is AJAX XmlHttpRequest Callbacks and Error Handling JSON Uses of AJAX 5 Interactivity To enable content to be brought in from the server in response to user requests Performance Load the most critical portions of a webpage first, and then load the rest asynchronously Security (this is questionable) Bring in only the code/data that is needed on demand to reduce the attack surface of the
    [Show full text]
  • The Study of Open Source Cmss by CHETAN GOPILAL JAIN a Thesis
    The Study of Open Source CMSs By CHETAN GOPILAL JAIN A thesis submitted to the Graduate School-New Brunswick Rutgers, The State University of New Jersey in partial fulfillment of the requirements for the degree of Master of Science Graduate Program in Electrical and Computer Engineering written under the direction of Prof Deborah Silver and approved by ________________________ ________________________ ________________________ ________________________ New Brunswick, New Jersey May, 2010 2010 CHETAN GOPILAL JAIN ALL RIGHTS RESERVED ABSTRACT OF THE THESIS The Study of Open Source CMSs By CHETAN JAIN Thesis Director: Professor Deborah Silver In this thesis, we evaluate different open source content management systems (CMSs) and determine their appropriateness for scientific research laboratories’ website content management. We describe different CMSs and evaluate them based on the following criteria: ease of installation, usability, maintenance and updates, scalability, community strength and support, user roles and workflow, security, and Web 2.0 features. We then choose of these system, Drupal, and demonstrate its effectiveness for two different scientific websites, Bio-1 and Vizlab. Drupal allows integrating new features using community contributed modules and easy future up-gradation. Successful implementation of both projects using Drupal highlights the importance of Open Source CMSs. ii Acknowledgement I would like to thank my advisor, Prof. Deborah Silver, for her support and encouragement while writing this thesis.Also, I would like to thank my parents and family who provided me with a strong educational foundation and supported me in all my academic pursuits. I also acknowledge the help of VIZLAB at Rutgers. iii Table of Contents Abstract ……………………………………………………………………….………………….ii Acknowledgement …………………………………………………………...………………...
    [Show full text]
  • Specification for JSON Abstract Data Notation Version
    Standards Track Work Product Specification for JSON Abstract Data Notation (JADN) Version 1.0 Committee Specification 01 17 August 2021 This stage: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.html https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.pdf Previous stage: https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.html https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.pdf Latest stage: https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.html https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.pdf Technical Committee: OASIS Open Command and Control (OpenC2) TC Chair: Duncan Sparrell ([email protected]), sFractal Consulting LLC Editor: David Kemp ([email protected]), National Security Agency Additional artifacts: This prose specification is one component of a Work Product that also includes: JSON schema for JADN documents: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/schemas/jadn-v1.0.json JADN schema for JADN documents: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/schemas/jadn-v1.0.jadn Abstract: JSON Abstract Data Notation (JADN) is a UML-based information modeling language that defines data structure independently of data format.
    [Show full text]
  • The Internet in Iot—OSI, TCP/IP, Ipv4, Ipv6 and Internet Routing
    Chapter 2 The Internet in IoT—OSI, TCP/IP, IPv4, IPv6 and Internet Routing Reliable and efficient communication is considered one of the most complex tasks in large-scale networks. Nearly all data networks in use today are based on the Open Systems Interconnection (OSI) standard. The OSI model was introduced by the International Organization for Standardization (ISO), in 1984, to address this composite problem. ISO is a global federation of national standards organizations representing over 100 countries. The model is intended to describe and standardize the main communication functions of any telecommunication or computing system without regard to their underlying internal structure and technology. Its goal is the interoperability of diverse communication systems with standard protocols. The OSI is a conceptual model of how various components communicate in data-based networks. It uses “divide and conquer” concept to virtually break down network communication responsibilities into smaller functions, called layers, so they are easier to learn and develop. With well-defined standard interfaces between layers, OSI model supports modular engineering and multivendor interoperability. 2.1 The Open Systems Interconnection Model The OSI model consists of seven layers as shown in Fig. 2.1: physical (Layer 1), data link (Layer 2), network (Layer 3), transport (Layer 4), session (Layer 5), presentation (Layer 6), and application (Layer 7). Each layer provides some well-defined services to the adjacent layer further up or down the stack, although the distinction can become a bit less defined in Layers 6 and 7 with some services overlapping the two layers. • OSI Layer 7—Application Layer: Starting from the top, the application layer is an abstraction layer that specifies the shared protocols and interface methods used by hosts in a communications network.
    [Show full text]
  • Open Message Queue Mq.Dev.Java.Net
    Open Message Queue mq.dev.java.net Jason Huang Technical Consultant Sun Microsystems, Inc. 1 Objective Understand basic of JMS API and OpenMQ products Copyright 2007 Sun Microsystems Inc. 2 Agenda • Introduction to JMS • What's OpenMQ • Features of OpenMQ • Demo Copyright 2007 Sun Microsystems Inc. 3 What is Java Message Service? • A Java API for Message Oriented Middleware(MOM) > JMS is a specification developed under the Java Community Process as JSR 914. > http://www.jcp.org/en/jsr/detail?id=914 Copyright 2007 Sun Microsystems Inc. 4 What Is Java Message Service? • The Java 2 Platform, Enterprise Edition (J2EE™platform) specification for MOM products • Defines provider-neutral APIs and administered objects that allow client applications to be portable across Java Message Service providers • Is defined as part of the J2EE 1.3 and later specification Copyright 2007 Sun Microsystems Inc. 5 What Is Java Message Service (continued)? • Supports two different messaging models: point-to-point and publish-subscribe • Supports asynchronous messaging and message-driven beans (MDBs) on a J2EE application server • Allows providers to implement additional provider-specific features • Provides the ability to tune applications for performance and reliability Copyright 2007 Sun Microsystems Inc. 6 Point to Point Messaging Message Service Producers Consumers Sender Receiver Queue 1 Queue 2 Receiver Queue 3 Receiver Messages from producers delivered to consumers Held in Queue Delivered, in order – Guaranteed Copyright 2007 Sun Microsystems Inc. 7 Publish and Subscribe Messaging Message Service Producers Consumers Publisher Subscriber Topic Subscriber Subscriber Publishers are independent from subscribers Message expiration is configured Subscriptions may be “durable” Copyright 2007 Sun Microsystems Inc.
    [Show full text]
  • Jersey 1.8 User Guide Jersey 1.8 User Guide Table of Contents
    Jersey 1.8 User Guide Jersey 1.8 User Guide Table of Contents Preface ............................................................................................................................ ix 1. Getting Started ............................................................................................................... 1 1.1. Creating a root resource ........................................................................................ 2 1.2. Deploying the root resource ................................................................................... 3 1.3. Testing the root resource ....................................................................................... 3 1.4. Here's one Paul created earlier ................................................................................ 4 2. Overview of JAX-RS 1.1 ................................................................................................. 5 2.1. Root Resource Classes .......................................................................................... 5 2.1.1. @Path ...................................................................................................... 5 2.1.2. HTTP Methods .......................................................................................... 6 2.1.3. @Produces ................................................................................................ 7 2.1.4. @Consumes .............................................................................................. 9 2.2. Deploying a RESTful Web Service .........................................................................
    [Show full text]
  • Sustainability Forecasting for Apache Incubator Projects
    Sustainability Forecasting for Apache Incubator Projects Likang Yin Zhuangzhi Chen DECAL and CS Department College of Information Engineering University of California, Davis Zhejiang University of Technology [email protected] [email protected] Qi Xuan Vladimir Filkov College of Information Engineering DECAL and CS Department Zhejiang University of Technology University of California, Davis [email protected] [email protected] ABSTRACT 80% of OSS projects become abandoned over time, especially the Although OSS development is very popular, ultimately more than smaller and younger projects [45]. Certainly not all OSS projects 80% of OSS projects fail. Identifying the factors associated with are meant to be widely used or even to persist beyond a college OSS success can help in devising interventions when a project semester. However, even the large, popular OSS software, widely takes a downturn. OSS success has been studied from a variety of used in our daily lives and by fortune 500 companies, started out angles, more recently in empirical studies of large numbers of di- as small projects. Thus, from a societal perspective it is important verse projects, using proxies for sustainability, e.g., internal metrics to ask: Why do some nascent OSS projects succeed and become related to productivity and external ones, related to community pop- self-sustaining while others do not [41]? And can the latter be ularity. The internal socio-technical structure of projects has also helped? been shown important, especially their dynamics. This points to To aid developer communities to build and maintain sustainable another angle on evaluating software success, from the perspective OSS projects, nonprofit organizations like the Apache Software of self-sustaining and self-governing communities.
    [Show full text]
  • Eclipse Glassfish Server Release Notes, Release 5.1 Table of Contents
    Eclipse GlassFish Server Release Notes, Release 5.1 Table of Contents Eclipse GlassFish Server . 1 Preface. 2 GlassFish Server Documentation Set. 2 Related Documentation. 4 Typographic Conventions. 5 Symbol Conventions . 5 Default Paths and File Names . 6 1 Eclipse GlassFish Server 6.1 Release Notes . 8 Revision History . 8 What’s New in the GlassFish Server 5.1 Release?. 9 Hardware and Software Requirements . 10 Known Issues in GlassFish Server 5.1 . 15 Restrictions and Deprecated Functionality . 17 Documentation Errata . 20 Features Available Only in the Full Platform . 20 Java EE Standards Support . 21 Java EE SDK . 23 How to Report Problems and Provide Feedback . 24 Additional Resources. 24 Eclipse GlassFish Server Eclipse GlassFish Server Release Notes Release 5.1 Contributed 2018, 2019 These Release Notes provide late-breaking information about GlassFish Server 5.1 software and documentation. Also included are a summary of new product features in the 5.1 release, and descriptions and workarounds for known issues and limitations. Eclipse GlassFish Server Release Notes, Release 5.1 Copyright © 2013, 2019 Oracle and/or its affiliates. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v. 2.0, which is available at http://www.eclipse.org/legal/epl-2.0. SPDX-License-Identifier: EPL-2.0 Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • Lecture: TCP/IP 2
    TCP/IP- Lecture 2 [email protected] How TCP/IP Works • The four-layer model is a common model for describing TCP/IP networking, but it isn’t the only model. • The ARPAnet model, for instance, as described in RFC 871, describes three layers: the Network Interface layer, the Host-to- Host layer, and the Process-Level/Applications layer. • Other descriptions of TCP/IP call for a five-layer model, with Physical and Data Link layers in place of the Network Access layer (to match OSI). Still other models might exclude either the Network Access or the Application layer, which are less uniform and harder to define than the intermediate layers. • The names of the layers also vary. The ARPAnet layer names still appear in some discussions of TCP/IP, and the Internet layer is sometimes called the Internetwork layer or the Network layer. [email protected] 2 [email protected] 3 TCP/IP Model • Network Access layer: Provides an interface with the physical network. Formats the data for the transmission medium and addresses data for the subnet based on physical hardware addresses. Provides error control for data delivered on the physical network. • Internet layer: Provides logical, hardware-independent addressing so that data can pass among subnets with different physical architectures. Provides routing to reduce traffic and support delivery across the internetwork. (The term internetwork refers to an interconnected, greater network of local area networks (LANs), such as what you find in a large company or on the Internet.) Relates physical addresses (used at the Network Access layer) to logical addresses.
    [Show full text]
  • Understanding JSON Schema Release 2020-12
    Understanding JSON Schema Release 2020-12 Michael Droettboom, et al Space Telescope Science Institute Sep 14, 2021 Contents 1 Conventions used in this book3 1.1 Language-specific notes.........................................3 1.2 Draft-specific notes............................................4 1.3 Examples.................................................4 2 What is a schema? 7 3 The basics 11 3.1 Hello, World!............................................... 11 3.2 The type keyword............................................ 12 3.3 Declaring a JSON Schema........................................ 13 3.4 Declaring a unique identifier....................................... 13 4 JSON Schema Reference 15 4.1 Type-specific keywords......................................... 15 4.2 string................................................... 17 4.2.1 Length.............................................. 19 4.2.2 Regular Expressions...................................... 19 4.2.3 Format.............................................. 20 4.3 Regular Expressions........................................... 22 4.3.1 Example............................................. 23 4.4 Numeric types.............................................. 23 4.4.1 integer.............................................. 24 4.4.2 number............................................. 25 4.4.3 Multiples............................................ 26 4.4.4 Range.............................................. 26 4.5 object................................................... 29 4.5.1 Properties...........................................
    [Show full text]
  • HTML5 Websocket Protocol and Its Application to Distributed Computing
    CRANFIELD UNIVERSITY Gabriel L. Muller HTML5 WebSocket protocol and its application to distributed computing SCHOOL OF ENGINEERING Computational Software Techniques in Engineering MSc arXiv:1409.3367v1 [cs.DC] 11 Sep 2014 Academic Year: 2013 - 2014 Supervisor: Mark Stillwell September 2014 CRANFIELD UNIVERSITY SCHOOL OF ENGINEERING Computational Software Techniques in Engineering MSc Academic Year: 2013 - 2014 Gabriel L. Muller HTML5 WebSocket protocol and its application to distributed computing Supervisor: Mark Stillwell September 2014 This thesis is submitted in partial fulfilment of the requirements for the degree of Master of Science © Cranfield University, 2014. All rights reserved. No part of this publication may be reproduced without the written permission of the copyright owner. Declaration of Authorship I, Gabriel L. Muller, declare that this thesis titled, HTML5 WebSocket protocol and its application to distributed computing and the work presented in it are my own. I confirm that: This work was done wholly or mainly while in candidature for a research degree at this University. Where any part of this thesis has previously been submitted for a degree or any other qualification at this University or any other institution, this has been clearly stated. Where I have consulted the published work of others, this is always clearly attributed. Where I have quoted from the work of others, the source is always given. With the exception of such quotations, this thesis is entirely my own work. I have acknowledged all main sources of help. Where the thesis is based on work done by myself jointly with others, I have made clear exactly what was done by others and what I have contributed myself.
    [Show full text]
  • Opening Plenary State of the Feather
    Opening Plenary Lars Eilebrecht V.P., Conference Planning at ASF and Lead for ApacheCon Europe 2009 State of the Feather Jim Jagielski Chairman, The Apache Software Foundation Welcome to Amsterdam Presented by The Apache Software Foundation Produced by Stone Circle Productions, Inc. Conference Program • Detailed conference program guide available as a PDF from the ApacheCon Web site – www.eu.apachecon.com • Printed Conference-at-a- Glance program available at registration desk Presentations • 4 Tracks every day starting at 9:00 • Presentation slides provided by speakers will be made available on the ApacheCon Web site during the conference Wednesday Special Events • 9:15-9:30: Jim Jagielski “State of the Feather” • 9:30-10:30: Raghu Ramakrishnan “Data Management in the Cloud” • 10:30-11:30: Arjé Cahn, Ajay Anand, Steve Loughran, and Mark Brewer “Panel: The Business of Open Source”, moderated by Sally Khudairi • 13:00-14:00: Lars Eilebrecht “Behind the Scenes of The ASF” Wednesday Special Events • 18:30-20:00: Welcome Reception and ASF 10th Anniversary Party – Celebrating a Decade of Open Source Leadership • 19:30: OpenPGP Key Signing – [email protected] – moderated by Jean-Frederic Clere Thursday Special Events • 13:00-14:00: Jim Jagielski “Sponsoring the ASF at the Corporate and Individual Level” • 17:30-18:30: James Governor “Open Sourcing The Analyst Business – Turning Prop. Knowledge Inside Out” • 18:30-20:00: “Lightning Talks”, mod. by Danese Cooper and Rich Bowen Friday Special Events • 11:30-13:00: Lars Eilebrecht, Dirk- Willem van Gulik, Jim Jagielski, Sally Khudairi, Cliff Skolnick, “Apache Pioneer's Panel – 10 years of the ASF”, mod.
    [Show full text]