Curriculum Vitae
Total Page：16
File Type：pdf, Size：1020Kb
Load more
Recommended publications
-
DIRECTOR's REPORT September 21, 2017
DIRECTOR’S REPORT September 21, 2017 SUMMER PROGRAMMING The 2017 Summer Reading Club (SRC), Read Up! Rise Up! by Design, utilized key aspects of the design thinking methodology in the development of the SRC program curriculum. Design thinking, as it relates to program development, seeks to identify creative solutions to problems by utilizing solution-based strategies. In an ideal setting these creative strategies ultimately result in a constructive resolution to an identified problem or challenge. The design thinking methodology is used in a variety of disciplines i.e. urban planning, web development, education etc. Programming content focused on S.T.R.E.A.M (Science, Technology, Reading, Writing, Engineering, Arts and Math) related subjects. Throughout the summer program participants participated in variety of enrichment activities that promoted creative thinking, problem solving, reading, writing and other forms of creative expression. Summer Reading Club registration began May 15th, 2017 with the contest and associated programming continuing for 9 weeks (June 5th – August 5th). 10,156 students registered for this year’s SRC with 5,286 participants completing. The 2017 completion rate continued its upward trend with 52% of all participants completing the program. The Cleveland Public Library received generous financial and in-kind support from the Friends of the Cleveland Public Library Foundation, The Cleveland Museum of Art, The City of Cleveland, Cleveland Fire Department, Cleveland Metropolitan School District, United Way of Greater Cleveland, Greater Cleveland Food Bank, KPMG, Mitchell’s Ice Cream, McDonalds, and Georgio’s Pizza. The Library was also the recipient of multiple book grants that enabled children to receive free books for participating in the program. -
Alternatives to Mvc for Web Applications
Alternatives To Mvc For Web Applications Cleveland twins her perambulation inly, she repulsed it tails. Sporty and protracted Morly lionizes skeptically and distilling his exotics upwardly and sanctifyingly. Intranational and sonsy Woodman still revisit his phelloderm somnolently. We offer vendors absolutely not for mvc promoted using dependency injection, view system and double click on. Web application framework which sheet a modelviewcontroller MVC. Vue is with excellent alternative framework to hustle and leverage as society need. Artisan console tab or http handler has no more streamlined for software components are alternatives to. At the application for no, we have better have to check if they come to connect you will tell what data. Api rest of time and validation components like this power a more direct instantiation of applications to for mvc web layer and examples of asp update this discussion comes at the model. In mvc pattern never be useful, mobile application will only difficult. 10 Node Frameworks to vent in 2019 Scotchio. What a point many systems too much more community will surely help you can modify or surnames of. Wrong way for web application to work on azure active scan does. The alternative to for. Which is for mac support for quick and quicker manner without obscuring node modules. React Flux vs MVC Javatpoint. Why MVC is better probe the Web Form C Corner. In any subscribed parties within asp update panels are. This web mvc frameworks and you and double detection after development of. Database for the alternate form of the asynchronous technique. 11 Python Frameworks for Web Development In 2021. -
Red Hat Enterprise Linux 6 Developer Guide
Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. -
GNU Build System
Maemo Diablo Reference Manual for maemo 4.1 GNU Build System December 22, 2008 Contents 1 GNU Build System 2 1.1 Introduction .............................. 2 1.2 GNU Make and Makefiles ...................... 2 1.2.1 Simplest Real Example .................... 3 1.2.2 Anatomy of Makefile ..................... 6 1.2.3 Default Goal .......................... 7 1.2.4 On Names of Makefiles ................... 7 1.2.5 Questions ........................... 8 1.2.6 Adding Make Goals ..................... 8 1.2.7 Making One Target at a Time ................ 9 1.2.8 PHONY Keyword ...................... 9 1.2.9 Specifying Default Goal ................... 10 1.2.10 Other Common Phony Goals ................ 11 1.2.11 Variables in Makefiles .................... 11 1.2.12 Variable Flavors ........................ 11 1.2.13 Recursive Variables ...................... 12 1.2.14 Simple Variables ....................... 13 1.2.15 Automatic Variables ..................... 14 1.2.16 Integrating with Pkg-Config ................ 15 1.3 GNU Autotools ............................ 16 1.3.1 Brief History of Managing Portability ........... 17 1.3.2 GNU Autoconf ........................ 18 1.3.3 Substitutions ......................... 22 1.3.4 Introducing Automake .................... 24 1.3.5 Checking for Distribution Sanity .............. 29 1.3.6 Cleaning up .......................... 29 1.3.7 Integration with Pkg-Config ................ 30 1 Chapter 1 GNU Build System 1.1 Introduction The following code examples are used in this chapter: simple-make-files • autoconf-automake • 1.2 GNU Make and Makefiles The make program from the GNU project is a powerful tool to aid implementing automation in the software building process. Beside this, it can be used to automate any task that uses files and in which these files are transformed into some other form. -
Secure Programming Practices Lecture 5 Error Handling
SWE 781 Secure Software Design and Programming Error Handling Lecture 5 Ron Ritchey, Ph.D. Chief Scientist 703/377.6704 [email protected] 0 Copyright Ronald W. Ritchey 2008, All Rights Reserved Schedule (tentative) Date Subject Sep 1st Introduction (today) ; Chess/West chapter 1, Wheeler chapters 1,2,3 Sep 8th Computer attack overview Sep 15th Input Validation; Chess/West chapter 5, Wheeler chapter 5 Sep 22nd Buffer Overflows; Chess/West chapters 6, 7; Wheeler chapter 6 Sep 29th Class Cancelled Oct 6th Error Handling; Chess/West chapter 8; Wheeler chapter 9 (9.1, 9.2, 9.3 only) Oct 13th Columbus Recess Oct 20th Mid-Term exam Oct 27th Mid Term Review / Major Assignment Introduction; Privacy, Secrets, and Cryptography; Chess/West chapter 11; Wheeler chapter 11 (11.3, 11.4, 11.5 only) Nov 3rd Implementing authentication and access control Nov 10th Web Application Vulnerabilities; Chess/West chapter 9,10 Nov 17th Secure programming best practices / Major Assignment Stage Check ; Chess/West chapter 12; Wheeler chapters 7,8,9,10 Nov 24th Static Code Analysis & Runtime Analysis Dec 1st The State of the Art (guest lecturer) Dec 8th TBD (Virtual Machines, Usability [phishing], E-Voting, Privilege Separation, Java Security, Network Security & Worms) 1 Copyright Ronald W. Ritchey 2008, All Rights Reserved Today’s Agenda * . Error Handling, What could possibly go wrong? . Handling return codes . Managing exceptions . Preventing resource leaks . Logging and debugging . Minor Assignment 3 * Today’s materials derive heavily from Chess/West, Securing Programming with Static Analysis 2 Copyright Ronald W. Ritchey 2008, All Rights Reserved Error Handling: What could possibly go wrong? 3 Copyright Ronald W. -
Sell-1647C , Stratiform, Massive Sulfide, Sedimentary Deposits
CONTACT INFORMATION Mining Records Curator Arizona Geological Survey 416 W. Congress St., Suite 100 Tucson, Arizona 85701 520-770-3500 http://www.azgs.az.gov [email protected] The following file is part of the James Doyle Sell Mining Collection ACCESS STATEMENT These digitized collections are accessible for purposes of education and research. We have indicated what we know about copyright and rights of privacy, publicity, or trademark. Due to the nature of archival collections, we are not always able to identify this information. We are eager to hear from any rights owners, so that we may obtain accurate information. Upon request, we will remove material from public view while we address a rights issue. CONSTRAINTS STATEMENT The Arizona Geological Survey does not claim to control all rights for all materials in its collection. These rights include, but are not limited to: copyright, privacy rights, and cultural protection rights. The User hereby assumes all responsibility for obtaining any rights to use the material in excess of “fair use.” The Survey makes no intellectual property claims to the products created by individual authors in the manuscript collections, except when the author deeded those rights to the Survey or when those authors were employed by the State of Arizona and created intellectual products as a function of their official duties. The Survey does maintain property rights to the physical and digital representations of the works. QUALITY STATEMENT The Arizona Geological Survey is not responsible for the accuracy of the records, information, or opinions that may be contained in the files. The Survey collects, catalogs, and archives data on mineral properties regardless of its views of the veracity or accuracy of those data. -
GNU Emacs Manual
GNU Emacs Manual GNU Emacs Manual Sixteenth Edition, Updated for Emacs Version 22.1. Richard Stallman This is the Sixteenth edition of the GNU Emacs Manual, updated for Emacs version 22.1. Copyright c 1985, 1986, 1987, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being \The GNU Manifesto," \Distribution" and \GNU GENERAL PUBLIC LICENSE," with the Front-Cover texts being \A GNU Manual," and with the Back-Cover Texts as in (a) below. A copy of the license is included in the section entitled \GNU Free Documentation License." (a) The FSF's Back-Cover Text is: \You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development." Published by the Free Software Foundation 51 Franklin Street, Fifth Floor Boston, MA 02110-1301 USA ISBN 1-882114-86-8 Cover art by Etienne Suvasa. i Short Contents Preface ::::::::::::::::::::::::::::::::::::::::::::::::: 1 Distribution ::::::::::::::::::::::::::::::::::::::::::::: 2 Introduction ::::::::::::::::::::::::::::::::::::::::::::: 5 1 The Organization of the Screen :::::::::::::::::::::::::: 6 2 Characters, Keys and Commands ::::::::::::::::::::::: 11 3 Entering and Exiting Emacs ::::::::::::::::::::::::::: 15 4 Basic Editing -
Downloads." the Open Information Security Foundation
Performance Testing Suricata The Effect of Configuration Variables On Offline Suricata Performance A Project Completed for CS 6266 Under Jonathon T. Giffin, Assistant Professor, Georgia Institute of Technology by Winston H Messer Project Advisor: Matt Jonkman, President, Open Information Security Foundation December 2011 Messer ii Abstract The Suricata IDS/IPS engine, a viable alternative to Snort, has a multitude of potential configurations. A simplified automated testing system was devised for the purpose of performance testing Suricata in an offline environment. Of the available configuration variables, seventeen were analyzed independently by testing in fifty-six configurations. Of these, three variables were found to have a statistically significant effect on performance: Detect Engine Profile, Multi Pattern Algorithm, and CPU affinity. Acknowledgements In writing the final report on this endeavor, I would like to start by thanking four people who made this project possible: Matt Jonkman, President, Open Information Security Foundation: For allowing me the opportunity to carry out this project under his supervision. Victor Julien, Lead Programmer, Open Information Security Foundation and Anne-Fleur Koolstra, Documentation Specialist, Open Information Security Foundation: For their willingness to share their wisdom and experience of Suricata via email for the past four months. John M. Weathersby, Jr., Executive Director, Open Source Software Institute: For allowing me the use of Institute equipment for the creation of a suitable testing -
Using GNU Autotools to Manage a “Minimal Project”
05AAL Ch 04 9/12/00 10:14 AM Page 21 4 Using GNU Autotools to Manage a “Minimal Project” This chapter describes how to manage a minimal project using the GNU Autotools. For this discussion, a minimal project refers to the smallest possible project that can still illustrate a sufficient number of principles related to using the tools. Studying a smaller project makes it easier to understand the more complex interactions between these tools when larger projects require advanced features. The example project used throughout this chapter is a fictitious command interpreter called ‘foonly’. ‘foonly’ is written in C, but like many interpreters, uses a lexical analyzer and a parser expressed using the lex and yacc tools. The package is developed to adhere to the GNU ‘Makefile’ standard, which is the default behavior for Automake. This project does not use many features of the GNU Autotools. The most note- worthy one is libraries; this package does not produce any libraries of its own, so Libtool does not feature them in this chapter. The more complex projects presented in Chapter 7, “A Small GNU Autotools Project” and Chapter 11, “A Large GNU Autotools Project” illustrate how Libtool participates in the build system. The essence of this chapter is to provide a high-level overview of the user-written files and how they interact. 4.1 User-Provided Input Files The smallest project requires the user to provide only two files. The GNU Autotools generate the remainder of the files needed to build the package are in Section 4.2, “Generated Output Files.” -
The Starlink Build System SSN/78.1 —Abstract I
SSN/78.1 Starlink Project Starlink System Note 78.1 Norman Gray, Peter W Draper, Mark B Taylor, Steven E Rankin 11 April 2005 Copyright 2004-5, Council for the Central Laboratory of the Research Councils Copyright 2007, Particle Physics and Astronomy Research Council Copyright 2007, Science and Technology Facilities Council The Starlink Build System SSN/78.1 —Abstract i Abstract This document provides an introduction to the Starlink build system. It describes how to use the Starlink versions of the GNU autotools (autoconf, automake and libtool), how to build the software set from a checkout, how to add and configure new components, and acts as a reference manual for the Starlink-specific autoconf macros and Starlink automake features. It does not describe the management of the CVS repository in detail, nor any other source maintainance patterns. It should be read in conjunction with the detailed build instructions in the README file at the top of the source tree (which takes precedence over any instructions in this document, though there should be no major disagreements), and with sun248, which additionally includes platform-specific notes. Copyright 2004-5, Council for the Central Laboratory of the Research Councils Copyright 2007, Particle Physics and Astronomy Research Council Copyright 2007, Science and Technology Facilities Council ii SSN/78.1—Contents Contents 1 Introduction 1 1.1 Quick entry-points . 2 2 Tools 3 2.1 Overview of the Autotools . 3 2.1.1 Autoconf . 5 2.1.2 Automake . 9 2.1.3 Libtool . 13 2.1.4 Autoreconf: why you don’t need to know about aclocal . -
Autotools Tutorial
Autotools Tutorial Mengke HU ECE Department Drexel University ASPITRG Group Meeting Outline 1 Introduction 2 GNU Coding standards 3 Autoconf 4 Automake 5 Libtools 6 Demonstration The Basics of Autotools 1 The purpose of autotools I It serves the needs of your users (checking platform and libraries; compiling and installing ). I It makes your project incredibly portablefor dierent system platforms. 2 Why should we use autotools: I A lot of free softwares target Linux operating system. I Autotools allow your project to build successfully on future versions or distributions with virtually no changes to the build scripts. The Basics of Autotools 1 The purpose of autotools I It serves the needs of your users (checking platform and libraries; compiling and installing ). I It makes your project incredibly portablefor dierent system platforms. 2 Why should we use autotools: I A lot of free softwares target Linux operating system. I Autotools allow your project to build successfully on future versions or distributions with virtually no changes to the build scripts. The Basics of Autotools 1 3 GNU packages for GNU build system I Autoconf Generate a conguration script for a project I Automake Simplify the process of creating consistent and functional makeles I Libtool Provides an abstraction for the portable creation of shared libraries 2 Basic steps (commends) to build and install software I tar -zxvf package_name-version.tar.gz I cd package_name-version I ./congure I make I sudo make install The Basics of Autotools 1 3 GNU packages for GNU build -
Supporting the Development Process of the Datagrid Workload Management System Software with GNU Autotools, CVS And
Supporting the Development Process of the DataGrid Workload Management ∗ System Software with GNU autotools, CVS and RPM A. Gianelle, R. Pelusoy , M. Sgaravatto, INFN Sezione di Padova, Via Marzolo 8, I-35131 Padova, Italy F. Giacomini, E. Ronchieriz , INFN CNAF, Viale Berti Pichat 6/2 , I-40127 Bologna, Italy G. Avellino, B. Cantalupo, S. Beco, A. Maraschini, F. Pacini, DATAMAT S.p.A., Via Laurentina 760, I-00143 Roma, Italy A. Guarise, R. Piro, A. Werbrouck, INFN Sezione di Torino, Via P. Giuria 1, I-10125 Torino, Italy D. Kouril, A. Krenek, Z. Kabela, L. Matyska, M. Mulac, J. Pospisil, M. Ruda., Z. Salvet, J. Sitera, M. Vocu, CESNET z.s.p.o., Zikova 4, 160 00 Praha 6, Czech Republic M. Mezzadri, F. Prelzx , INFN Sezione di Milano, Via Celoria, 16, I-20133 Milano, Italy S. Monforte, M. Pappalardo, INFN Sezione di Catania, Via S. Sofia 64, I-95123 Catania, Italy D. Colling, Imperial College London, Blackett Laboratory, Prince Consort Road, London, SW7 2BW, UK Abstract The EDG WMS package contains daemons, libraries, test programs, documentation, etc. It is divided into com- Supporting the development of the Workload Manage- ponents that encapsulate independent functionalities part ment System in the context of the European DataGrid was of the package. The whole package is organised in a sin- a challenging task as the team was characterized by a high gle directory tree. Each component is identified by a sub- geographic and administrative dispersion, with developers directory and the main directory name is “workload”. Fur- distributed in various institutions and countries. Further, ther levels are present inside each component sub-directory.