DOCSLIB.ORG

Implementation of Android Based Mobile Phone Crawlers

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Implementation of Android Based Mobile Phone Crawlers International Journal of Mathematics and Computer Applications Research (IJMCAR) ISSN 2249-6955 Vol. 3, Issue 2, Jun 2013, 175-182 ©TJPRC Pvt. Ltd. IMPLEMENTATION OF ANDROID BASED MOBILE PHONE CRAWLERS SRASHTI GUPTA1 & KUNAL GUPTA2 1Student, Amity University, Noida, Uttar Pradesh, India 2Assistant Professor, Amity University, Noida, Uttar Pradesh, India ABSTRACT As mobile applications become more difficult, precise development tools and frameworks as well as cost valuable testing techniques and tools will be necessary to assure the development of secure, high-quality mobile applications. This paper concentrates on the mobile crawling in Android platform, and represents a technique for rapid crawling of Android applications. The procedure is based on a crawler that automatically searches a model and obtains result that can be automatically executed. This technique is supported by a tool for both crawl the data and generating the result. In the paper we present an example of using the technique and the tool for crawl a file which has mp3, txt etc extension by using Android application that preliminary shows the effectiveness and usability of the proposed approach. By using that crawler system the data is secure and easy to handle in an organization. KEYWORDS: Android Application, Crawling, Mobile Phone Crawlers, Security INTRODUCTION The mobile progress community is at a tipping point. Mobile users insist more choice, more prospects to customize their phones, and more functionality. Mobile operators want to provide value-added content to their subscribers in a convenient and profitable way. Mobile developers want the liberty to develop the powerful mobile applications users demand with minimal roadblocks to victory. Finally, handset manufacturers want a steady, protected, and reasonable platform to power their devices [3]. Up until now particular mobile platform has sufficiently addressed the needs of all the parties. Enter Android, which is a possible game-changer for the mobile development community. An innovative and open platform, Android is well positioned to address the growing needs of the mobile marketplace. It proposes an alternative approach to Mobile crawling based on mobile phone crawlers. Crawler mobility permits for more difficult crawling algorithms and avoids some of the inefficiencies linked with the brute force strategies exercised by current crawlers. By looking at the common structure of traditional search engines, it recognized that their planning is strictly centralized while the data being accessed by search engine crawlers is extremely scattered. If here apply a stationary crawler, firstly it would download many pages from Mobile Phones, which are detached immediately because they do not meet the theme area of the search engine. Perceptibly, this behavior is not very attractive because network bandwidth is exhausted by downloading unrelated information. Here it illustrate mobility in the context of Mobile crawling as the capability of a crawler to transfer itself to every Mobile Phone of notice before assembling pages on that Phone. After finishing the collection process on a particular Phone, the crawler together with the collected data travels to the next Phone or to its Network. Mobile crawlers are managed by a crawler manager (CM) which supplies each crawler with a record of target Mobile Phones and monitors the position of each crawler. In addition, the crawler manager provides the necessary functionality for pull out the collected data from the crawler for use by the indexer. 176 Srashti Gupta & Kunal Gupta Figure 1: Architecture of Proposed Android Based Mobile Crawler Powerful Development Framework Easily optimize a single binary for phones, tablets, and other devices. Android gives each and everything to user which they needed to build best in class familiarity. It gives a single application representation that organize apps broadly to hundreds of millions of users diagonally a wide range of devices—from phones to tablets and beyond. Android tools for creating apps that look great and take benefit of the hardware capabilities available on each device [13]. It repeatedly adapts your User Interface (UI) to look its best on each device, while giving you as much control as you want over your UI on dissimilar device types. For Example, It can create single app binary that’s optimized for both phone and tablet form factors. It announce UI in lightweight sets of XML resources, one set for parts of the UI that are common to all form factors and other sets for optimizations precise to phones or tablets [14]. At run time, Android applies the correct resource sets based on its screen size, density, locale, and so on. To help you develop efficiently, Android Developer Tools offer a full Java IDE with superior features for developing, debugging, and packaging Android apps [2]. Using the IDE, you can expand on any available Android device or create virtual policies that emulate any hardware configuration. QUALITIES FOR MOBILE PHONE CRAWLER The main benefit of the mobile crawling approach is that it permits to allocate crawling functionality within a distributed system such as the Web. Particularly, the following four qualities plays major role in this system: Localized Data Access Due to the HTTP request/response pattern, downloading the contents from a Web server engross important overhead due to request messages which have to be sent for every mobile page separately. This approach still requires one HTTP request per document but there is no need to broadcast these requests over the system any longer. Using a mobile crawler we reduce the HTTP overhead by shifting the crawler to the supply of the data. The crawler can then issue all HTTP requests locally with respect to the HTTP server. Remote Page Selections Mobile crawlers utilize the query shipping approach of database systems because all the information desirable to identify the relevant data portion is transferred directly to the data source along with the mobile crawler. After the query has been performed remotely, only the query result is transferred over the network and can be used to establish the preferred index without requiring any extra analysis. Implementation of Android Based Mobile Phone Crawlers 177 Remote Page Filtering Remote page filtering enlarges the concept of remote page selection to the contents of a Web page [4]. The thought behind remote page filtering is to allow the crawler to control the granularity of the data it retrieves. Depending on the ratio of relevant to irrelevant information, important portions of network bandwidth are wasted by transmitting ineffectual data [11]. A mobile crawler defeats this problem since it can filter out all irrelevant page portions keeping only information which is applicable with respect to the search engine the crawler is working for. Remote Page Compressions In order to decrease the quantity of data that has to be transmitted back to the crawler organizer, it introduces remote page compression as another basic feature of mobile crawlers [2]. In order to decrease the bandwidth required to transfer the crawler along with the data it holds back to the search engine, the mobile crawler applies compression procedures to reduce its size earlier to transmission. SOFTWARE USED IN CRAWLING In this section be going to to present the software which is used in different mobile phone systems. The basic fundamental technologies are HTML, XHTML, WAP, WML, CSS, ECMA Script. Table 1: Browsers in Various Mobile Systems Browser Origin Used in Android browser Google Nexus BlackBerry Browser Research in Motion - Blazer Palm installed on all newer Palm Treos and PDAs Internet Explorer Mobile Microsoft Samsung newer versions Firefox for mobile Mozilla Nokia Maemo and for Android Acquired by Research in Motion - No longer supports Iris Browser Torch Mobile Inc. Windows Mobile or Linux Capable of reading HTML and reformat for small Opera Mobile Opera Software screens, installed on many phones NetFront ACCESS Co.,ltd - Obigo Browser Obigo AB 100% owned by Teleca AB PlayStation Portable web browser Sony Sony PSP Myriad Browser (Previously Myriad Group Acquired from Openwave in 2008 Openwave Mobile Browser) Nokia, Samsung, LG Electronics, KYOCERA and other Polaris Browser Infraware Inc. Smartphone and cellular phone in USA, China, Korea, etc Renders Flash 10, Ajax and Silverlight content. supports Skyfire Mobile Browser Skyfire Windows Mobile 5/6.x,Symbian S60 and Android. Safari Apple Inc on iPhone, iPod Touch and iPad on Samsung, LG Electronics and other smartphones and uZard Web Logicplant Co., Ltd. cellular phones in Korea Kindle Basic Web Amazon.com Blackberry WebOS Browser Palm - xScope xScope Mobile on android systems Table 1 record the compilation of various browsers in use by special Mobile phones systems from the mobile crawler using GPRS. 178 Srashti Gupta & Kunal Gupta A TECHNIQUE FOR ANDROID MOBILE PHONE CRAWLERS Figure 2: The Crawling Algorithm DEVELOPING APPLICATION FOR MOBILE PHONE CRAWLER Commonly Used Packages With Android, mobile developers no longer have to reinvent the controls. Instead, developers use recognizable class libraries exposed through Android’s Java packages to execute common tasks such as graphics, database access, network access, secure communications, and utilities (such as XML parsing) [13]. The Android packages include support for Common user interface widgets (Buttons, Spin Controls,Text Input) User interface layout Secure networking and Web browsing features (SSL,WebKit)
Load more

Recommended publications
  • A Taxonomy and Business Analysis for Mobile Web Applications
    A Taxonomy and Business Analysis for Mobile Web Applications Kevin Hao Liu Working Paper CISL# 2009-01 January 2009 Composite Information Systems Laboratory (CISL) Sloan School of Management, Room E53-320 Massachusetts Institute of Technology Cambridge, MA 02142 A Taxonomy and Business Analysis for Mobile Web Applications By Kevin Hao Liu Ph.D. Computer Science Victoria University Submitted to the System Design and Management Program in Partial Fulfillment of the Requirements for the Degree of Master of Science in Management and Engineering At the Massachusetts Institute of Technology February 2009 © 2009 Kevin H Liu. All rights reserved The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part in any medium now known or hereafter created. Signature of Author Kevin H Liu System Design and Management Program February 2009 Certified by Stuart E Madnick John Norris Maguire Professor of Information Technology Sloan School of Management Professor of Engineering Systems School of Engineering Massachusetts Institute of Technology Thesis Supervisor Certified by Patrick Hale Director System Design & Management Program Massachusetts Institute of Technology A Taxonomy and Business Analysis for Mobile Web Applications By Kevin Hao Liu Submitted to the System Design and Management Program in February 2009 in Partial Fulfillment of the Requirements for the Degree of Master of Science in Management and Engineering ABSTRACT Mobile web applications refer to web applications on mobile devices, aimed at personalizing, integrating, and discovering mobile contents in user contexts. This thesis presents a comprehensive study of mobile web applications by proposing a new taxonomy for mobile web applications, and conducting a business analysis in the field of mobile web applications.
    [Show full text]
  • HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014
    HTTP cookie - Wikipedia, the free encyclopedia 14/05/2014 Create account Log in Article Talk Read Edit View history Search HTTP cookie From Wikipedia, the free encyclopedia Navigation A cookie, also known as an HTTP cookie, web cookie, or browser HTTP Main page cookie, is a small piece of data sent from a website and stored in a Persistence · Compression · HTTPS · Contents user's web browser while the user is browsing that website. Every time Request methods Featured content the user loads the website, the browser sends the cookie back to the OPTIONS · GET · HEAD · POST · PUT · Current events server to notify the website of the user's previous activity.[1] Cookies DELETE · TRACE · CONNECT · PATCH · Random article Donate to Wikipedia were designed to be a reliable mechanism for websites to remember Header fields Wikimedia Shop stateful information (such as items in a shopping cart) or to record the Cookie · ETag · Location · HTTP referer · DNT user's browsing activity (including clicking particular buttons, logging in, · X-Forwarded-For · Interaction or recording which pages were visited by the user as far back as months Status codes or years ago). 301 Moved Permanently · 302 Found · Help 303 See Other · 403 Forbidden · About Wikipedia Although cookies cannot carry viruses, and cannot install malware on 404 Not Found · [2] Community portal the host computer, tracking cookies and especially third-party v · t · e · Recent changes tracking cookies are commonly used as ways to compile long-term Contact page records of individuals' browsing histories—a potential privacy concern that prompted European[3] and U.S.
    [Show full text]
  • Web Crawler in Mobile Systems
    International Journal of Machine Learning and Computing, Vol. 2, No. 4, August 2012 Web Crawler in Mobile Systems Pavalam S. M., S. V. Kasmir Raja, Jawahar M., and Felix K. Akorli the crawler, Section 3 discusses the different types of Abstract—With the advent of internet technology, data has crawlers, and Section 4 explores the software used in mobile exploded to a considerable amount. Large volumes of data can phones for crawling purposes with Section 5 discusses the be explored easily through search engines, to extract valuable advantages that crawlers can bring in mobile information. Web crawlers are an indispensible part of search communications and section 6 brings out the summary. engine, which are program (proceeds with the search term) that can traverse through the hyperlinks, indexes them, parses the files and adds new links in to its queue and the mentioned process is done several times until search term vanishes from II. ARCHITECTURE OF A CRAWLER those pages. The web crawler looks for updating the links which Web crawler (also known as Spiders or robots) is software has already been indexed. This paper briefly reviews the concepts of web crawler, its architecture and its different types. that can start with a Uniform Resource Locator (known as It lists the software used by various mobile systems and also seed URL), downloads the pages with associated links and explores the ways of usage of web crawler in mobile systems and looks for the updates and stores them for later use. This reveals the possibility for further research. process is done iteratively.
    [Show full text]
  • Iris: Third-Party Authentication Service
    Iris: Third-Party Authentication Service Akshay Padmanabha Kevin Chen [email protected] [email protected] Surya Bhupatiraju Thomas Zhang [email protected] [email protected] ABSTRACT thentication and providing a centralized identification sys- Existing centralized identification systems, such as Facebook tem. To this end, we propose Iris: a web-based, secure, or Google, offer convenient services for authentication and centralized system to allow users to fully control what in- storing user information that third-party services leverage to formation they expose to third-party services, and offer full reduce friction and streamline the process of creating user transparency as to what data is collected and how it is used. profiles and logging in. However, these systems present con- flict of interests, and users may be interested in a third-party 2. PREVIOUS WORK service that focuses exclusively on authentication. To this A notable example of work towards an unbiased, third- end, we present Iris, a web-based, secure solution that re- party identification system is OpenID [6]. OpenID is a bold solves the single-point-of-failure concern and provides secure attempt in this direction, but faced many problems. One of protocols of data transmission and transparency of data us- the primary drawbacks include bad communication; it is not age. clear to end users as to how OpenID works or how it is used. Iris consists of two components: a database that holds This lack of understanding, along with poor implementation, users' information encrypted with their passphrases along security vulenerabilities, and trust issues, eventually led to with a public API to retreive this data, and a client-side OpenID becoming less and less popular.
    [Show full text]
  • Taxonomy of Mobile Web Applications from a Taxonomy and Business Analysis for Mobile Web Applications
    Chapter 3: Taxonomy of Mobile Web Applications from A Taxonomy and Business Analysis for Mobile Web Applications By Kevin Hao Liu Ph.D. Computer Science Victoria University Submitted to the System Design and Management Program in Partial Fulfillment of the Requirements for the Degree of Master of Science in Management and Engineering At the Massachusetts Institute of Technology February 2009 © 2009 Kevin H Liu. All rights reserved The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part in any medium now known or hereafter created. ABSTRACT Mobile web applications refer to web applications on mobile devices, aimed at personalizing, integrating, and discovering mobile contents in user contexts. This thesis presents a comprehensive study of mobile web applications by proposing a new taxonomy for mobile web applications, and conducting a business analysis in the field of mobile web applications. The thesis reviews the current surrounding environment for mobile web applications, namely, web 2.0 and 3.0, wireless communication technology, and Smartphone platform. The recent entry and success of Apple’s iPhone greatly enhanced the public awareness of the Smartphone technology. Google’s release of open-source Android platform and T-Mobile’s deployment of Android-powered “Dream” Smartphone not only intensify the competition among suppliers, but also provide an open-source foundation for mobile web applications. This thesis introduces a new mobile web application taxonomy to systematically study the values and the groupings of the mobile web applications. By introducing features and categories, the taxonomy provides a framework so the related companies and businesses can be comparatively analyzed and summarized.
    [Show full text]
  • Webkit and Blink: Open Development Powering the HTML5 Revolution
    WebKit and Blink: Open Development Powering the HTML5 Revolution Juan J. Sánchez LinuxCon 2013, New Orleans Myself, Igalia and WebKit Co-founder, member of the WebKit/Blink/Browsers team Igalia is an open source consultancy founded in 2001 Igalia is Top 5 contributor to upstream WebKit/Blink Working with many industry actors: tablets, phones, smart tv, set-top boxes, IVI and home automation. WebKit and Blink Juan J. Sánchez Outline The WebKit technology: goals, features, architecture, code structure, ports, webkit2, ongoing work The WebKit community: contributors, committers, reviewers, tools, events How to contribute to WebKit: bugfixing, features, new ports Blink: history, motivations for the fork, differences, status and impact in the WebKit community WebKit and Blink Juan J. Sánchez WebKit: The technology WebKit and Blink Juan J. Sánchez The WebKit project Web rendering engine (HTML, JavaScript, CSS...) The engine is the product Started as a fork of KHTML and KJS in 2001 Open Source since 2005 Among other things, it’s useful for: Web browsers Using web technologies for UI development WebKit and Blink Juan J. Sánchez Goals of the project Web Content Engine: HTML, CSS, JavaScript, DOM Open Source: BSD-style and LGPL licenses Compatibility: regression testing Standards Compliance Stability Performance Security Portability: desktop, mobile, embedded... Usability Hackability WebKit and Blink Juan J. Sánchez Goals of the project NON-goals: “It’s an engine, not a browser” “It’s an engineering project not a science project” “It’s not a bundle of maximally general and reusable code” “It’s not the solution to every problem” http://www.webkit.org/projects/goals.html WebKit and Blink Juan J.
    [Show full text]
  • Webkit and Blink: Bridging the Gap Between the Kernel and the HTML5 Revolution
    WebKit and Blink: Bridging the Gap Between the Kernel and the HTML5 Revolution Juan J. Sánchez LinuxCon Japan 2014, Tokyo Myself, Igalia and WebKit Co-founder, member of the WebKit/Blink/Browsers team Igalia is an open source consultancy founded in 2001 Igalia is Top 5 contributor to upstream WebKit/Blink Working with many industry actors: tablets, phones, smart tv, set-top boxes, IVI and home automation. WebKit and Blink Juan J. Sánchez Outline 1 Why this all matters 2 2004-2013: WebKit, a historical perspective 2.1. The technology: goals, features, architecture, ports, webkit2, code, licenses 2.2. The community: kinds of contributors and contributions, tools, events 3 April 2013. The creation of Blink: history, motivations for the fork, differences and impact in the WebKit community 4 2013-2014: Current status of both projects, future perspectives and conclusions WebKit and Blink Juan J. Sánchez PART 1: Why this all matters WebKit and Blink Juan J. Sánchez Why this all matters Long time trying to use Web technologies to replace native totally or partially Challenge enabled by new HTML5 features and improved performance Open Source is key for innovation in the field Mozilla focusing on the browser WebKit and now Blink are key projects for those building platforms and/or browsers WebKit and Blink Juan J. Sánchez PART 2: 2004-2013 WebKit, a historical perspective WebKit and Blink Juan J. Sánchez PART 2.1 WebKit: the technology WebKit and Blink Juan J. Sánchez The WebKit project Web rendering engine (HTML, JavaScript, CSS...) The engine is the product Started as a fork of KHTML and KJS in 2001 Open Source since 2005 Among other things, it’s useful for: Web browsers Using web technologies for UI development WebKit and Blink Juan J.
    [Show full text]
  • Building a Browser for Automotive: Alternatives, Challenges and Recommendations
    Building a Browser for Automotive: Alternatives, Challenges and Recommendations Juan J. Sánchez Automotive Linux Summit 2015, Tokyo Myself, Igalia and Webkit/Chromium Co-founder of Igalia Open source consultancy founded in 2001 Igalia is Top 5 contributor to upstream WebKit/Chromium Working with many industry actors: automotive, tablets, phones, smart tv, set-top boxes, IVI and home automation Building a Browser for Automotive Juan J. Sánchez Outline 1 A browser for automotive: requirements and alternatives 2 WebKit and Chromium, a historical perspective 3 Selecting between WebKit and Chromium based alternatives Building a Browser for Automotive Juan J. Sánchez PART 1 A browser for automotive: requirements and alternatives Building a Browser for Automotive Juan J. Sánchez Requirements Different User Experiences UI modifications (flexibility) New ways of interacting: accessibility support Support of specific standards (mostly communication and interfaces) Portability: support of specific hardware boards (performance optimization) Functionality and completeness can be less demanding in some cases (for now) Provide both browser as an application and as a runtime Building a Browser for Automotive Juan J. Sánchez Available alternatives Option 1) Licensing a proprietary solution: might bring a reduced time-to-market but involves a cost per unit and lack of flexibility Option 2) Deriving a new browser from the main open source browser technologies: Firefox (Gecko) Chromium WebKit (Safari and others) Mozilla removed support in their engine for third
    [Show full text]
  • Apache Wookie (Incubating)
    Apache Wookie (Incubating) Creating your first widget Ross Gardler [email protected] http://incubator.apache.org/wookie Objective focussed outline • Creating a widget from the template • Running in developer mode • Modify the widget • Using external libraries • Using external APIs (not via the proxy) • Setting widget properties • Packaging for distribution Task focussed outline • Create a development environment • Create a hello world widget from supplied templates • Run Wookie in standalone mode • Edit the widget • Create a real widget with geo-lookup • Display map of current location • Store settings • Package widget as .wgt Development Environment Create Development Environment • What you need: – Wookie source code – Ant + Ivy – JDK – Your favourite editor • Javascript, HTML, CSS • Java (if you want to hack on the server) Using the Workshop CD • Copy the “wookie” folder to your preferred project location • Copy “apache-ant” into your preferred applications application directory • Install JDK from “java” folder • Configure your environment – Set ANT_HOME – Add $ANT_HOME/bin to your $PATH Your first widget Hello World! Create a Hello World Widget • Wookie comes with a skeleton widget template: cd $WOOKIE_HOME/widgets ant seed-widget • Answer some questions about your widget – Short Name: part1 – Description: Code from first practical session of Wookie training day – Default height: 320 – Default width: 200 • You now have a widget in $WOOKIE_HOME/widgets/[SHORT_NAME] Widget File Structure config.xml index.html <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="pragma" content="no-cache"/> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>part1</title> </head> <body> <h1>Hello World...</h1> </body> </html> Running Wookie in Developer Mode Developer mode allows easy building and testing of widgets Developer Mode • Building Wookie auto deploys all widgets in the $WOOKIE_HOME/widgets directory • We can run in development mode with: cd .
    [Show full text]
  • The Mobile Web Handbook Published 2014 by Smashing Magazine Gmbh, Freiburg, Germany
    The Mobile Web Handbook Published 2014 by Smashing Magazine GmbH, Freiburg, Germany. Printed in the EU. ISBN: 978-3-94454093-1. Cover Design, Illustrations and Layout by Stephen Hay. Copyeditor and Proofreader: Owen Gregory. Editing and Quality Control: Vitaly Friedman. eBook Production: Cosima Mielke. Typesetting: Markus Seyfferth. The Mobile Web Handbook was written by Peter-Paul Koch and reviewed by Stephanie and Bryan Rieger and Vasilis van Gemert. Links and updates of this book can be found at http://quirksmode.org/mobilewebhandbook. Get the book. Table of Contents Foreword Introduction 9 Chapter 1 The Mobile World 17 Chapter 2 Browser 45 Chapter 3 Android 67 Chapter 4 Viewports 85 Chapter 5 CSS 131 Chapter 6 Touch and Pointer Events 147 Chapter 7 Becoming a Mobile Web Developer 197 Chapter 8 The Future of the Web on Mobile 219 Introduction Introduction Introduction The Mobile Web Handbook explores the differences between mobile and desktop web development that we should be aware of when creating websites for both. It’s not very technical — there are only a dozen or so simple code examples. It discusses no libraries or tools. It’s about mobile web fundamentals. There is no mobile web distinct from the desktop web. Developing websites for mobile is pretty much the same as developing for desktop, especially now that responsive design techniques allow us to adapt our CSS layouts to both huge desktop screens and tiny mobile ones. Still, there’s “The Mobile Web” in the title of this book, and that’s not an oversight or marketing trick. It serves as a convenient shorthand for “touch-based small-screen web on more browsers than you’ve ever heard of.” Mobile web development is not fundamentally different from desktop, but there are subtle distinctions that may cause you trouble if you’re unaware of them.
    [Show full text]
  • Securegateway Server
    Open Source Used In Secure Gateway 2.26 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-135850904 Open Source Used In Secure Gateway 2.26 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-135850904 Contents 1.1 Apache Commons Codec 1.3. 1.1.1 Available under license 1.2 Apache Commons Configuration 1.6 1.2.1 Available under license 1.3 Apache Commons Lib Apache 2.0 1.3.1 Available under license 1.4 Apache HTTP Server 2.2.9 1.4.1 Available under license 1.5 Apache Jakarta Commons HttpClient 3.1 1.5.1 Available under license 1.6 Apache Jakarta Commons HttpClient 3.1 1.6.1 Available under license 1.7 Apache Log4j 1.2.16 1.7.1 Available under license 1.8 apache-log4j 1.2.15 :DUPLICATE 1.8.1 Available under license 1.9 apache-log4j 1.2.15 1.9.1 Available under license 1.10 bcprov-jdk16 1.36 1.10.1 Available under license 1.11 BouncyCastle 1.46 :ICS 1.11.1 Available under license 1.12 c3p0 0.9.1.2 1.12.1 Available under license 1.13 Codec 1.2 1.13.1
    [Show full text]
  • Sistema De Información Orientado a La Web Para El Seguimiento Y Control Del Capital Vital De La Fundación Colombia Somos Todos
    SISTEMA DE INFORMACIÓN ORIENTADO A LA WEB PARA EL SEGUIMIENTO Y CONTROL DEL CAPITAL VITAL DE LA FUNDACIÓN COLOMBIA SOMOS TODOS HERMES SAMIT CASTAÑO CARDOZO FELIPE ALONSO GALINDO LOZANO ALONSO OYOLA TRUJILLO UNIVERSIDAD COOPERATIVA DE COLOMBIA FACULTAD DE INGENIERÍA DE SISTEMAS IBAGUÉ, TOLIMA 2018 Este obra está bajo una licencia de Creative Commons Reconocimiento-NoComercial- SinObraDerivada 4.0 Internacional. SISTEMA DE INFORMACIÓN ORIENTADO A LA WEB PARA EL SEGUIMIENTO Y CONTROL DEL CAPITAL VITAL DE LA FUNDACIÓN COLOMBIA SOMOS TODOS HERMES SAMIT CASTAÑO CARDOZO FELIPE ALONSO GALINDO LOZANO ALONSO OYOLA TRUJILLO INFORME FINAL PRODUCTO DE LA PRÁCTICA EMPRESARIAL NO REMUNERADA EN CONVENIO CON LA FUNDACIÓN COLOMBIA SOMOS TODOS ASESOR: ING. DENNIS MARTINEZ DUQUE UNIVERSIDAD COOPERATIVA DE COLOMBIA FACULTAD DE INGENIERÍA DE SISTEMAS IBAGUÉ, TOLIMA 2018 1 2 NOTA DE ACEPTACIÓN 3 DEDICATORIA El proyecto producto de esta pasantía empresarial se la dedicamos a nuestras familias, ya que nuestra carrera sería nada sin su apoyo incondicional, carrera la cual culmina dando como fruto un sistema que reúne años de estudios, práctica, sacrificio, esfuerzo, y compromiso, sin nuestras familias no seríamos los hombres comprometidos a hacer la diferencia con nuestro conocimiento, enfocados al análisis y desarrollo de los sistemas emergentes, cumpliendo así con el Objeto de Estudio de nuestra honorable universidad, siendo el estudio de “La información, su gestión y seguridad, mediante la arquitectura de software y el desarrollo e implementación de aplicaciones
    [Show full text]