DOCSLIB.ORG

Introduction to Iot.Js

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduction to Iot.Js Introduction to IoT.js Tilmann Scheller Principal Compiler Engineer [email protected] Samsung Open Source Group Samsung Research UK OpenIoT Summit 2016 San Diego, USA, April 4 – 6, 2016 Samsung Open Source Group 1 Overview ● Introduction ● JerryScript ● IoT.js ● Memory consumption/Performance ● Demo ● Future work ● Summary Samsung Open Source Group 2 Introduction Samsung Open Source Group 3 What is IoT.js? ● A lightweight version of Node.js ● Attempt to bring the success of Node.js to the embedded world ● Retains backwards compatibility with Node.js as much as possible ● Runs on top of JerryScript Samsung Open Source Group 4 IoT Hardware http://postscapes.com/internet-of-things-hardware Samsung Open Source Group 5 What is JerryScript? ● A really lightweight JavaScript engine ● Has a base footprint of 10KB of RAM ● Optimized for microcontrollers ● Developed from scratch by Samsung Samsung Open Source Group 6 Why JavaScript on microcontrollers? ● There's a huge pool of JavaScript developers ● Opens up the possibility for web developers to easily write software for embedded devices ● Performance overhead of JavaScript less of an issue for control tasks ● Increased productivity, shorter time to market ● Ability to load code dynamically over the network ● Security: Executing JavaScript code is safer than executing arbitrary native code Samsung Open Source Group 7 Open source ● Actively developed on GitHub ● JerryScript and IoT.js are both open source released under the Apache 2.0 license ● Building up a community around IoT.js/JerryScript Samsung Open Source Group 8 JerryScript Samsung Open Source Group 9 JerryScript History ● Development started in June 2014 ● Released as open source in June 2015 ● JerryScript passed 100% of the test262 conformance test suite in August 2015 ● Rewritten compact byte code implementation landed in January 2016 ● Current focus on performance optimization Samsung Open Source Group 10 JerryScript ● Heavily optimized for a low memory footprint ● Interpreter-only ● Compact object representation ● Compressed pointers ● No AST, directly creating byte code ● Compact byte code heavily optimized for low memory consumption Samsung Open Source Group 11 JerryScript Portability ● Extremely portable ● Self-contained ● Small C library ● Can run bare-metal ● Supports the STM32F4, ESP8266 boards ● Runs on Linux/OS X as well Samsung Open Source Group 12 JerryScript ● Written in C99 ● About 74KLOC ● Code size ~190KB when compiled with GCC LTO for ARM Thumb-2 ● Implements the entire ECMAScript 5.1 standard, passes 100% of the test262 conformance test suite ● C API for embedding JerryScript ● Byte code snapshot feature Samsung Open Source Group 13 JerryScript C API Samsung Open Source Group 14 JerryScript C API Samsung Open Source Group 15 IoT.js Samsung Open Source Group 16 IoT.js ● Lightweight version of Node.js ● Focus on resource-constrained devices ● Tries to retain backwards compatibility ● Mostly written in JavaScript Samsung Open Source Group 17 IoT.js Architecture Samsung Open Source Group 18 IoT.js Modules ● Assert ● Net ● Buffer ● Modules ● DNS ● Process ● Events ● Stream ● File System ● Timers ● HTTP ● GPIO Samsung Open Source Group 19 Target hardware ● STM32F4 developer board ● Cortex-M4F clocked at 168 MHz ● 192KB of RAM ● 1MB of flash memory Samsung Open Source Group 20 NuttX ● Real-time operating system ● Open source (BSD license) ● Scales from 8-bit microcontrollers to 32-bit microcontrollers ● Supports the STM32F4 developer board Samsung Open Source Group 21 libtuv ● libuv - Support library for asynchronous I/O ● libtuv - Stripped down version of Libuv ● Runs on NuttX and Linux ● Experimental support for mbed OS Samsung Open Source Group 22 Memory consumption/ Performance Samsung Open Source Group 23 IoT.js - Memory consumption Test name IoT.js Node.js require('http') 40KB 6.70MB test_httpserver.js 80KB 8.63MB Measured on a Raspberry Pi 2 Samsung Open Source Group 24 SunSpider 1.0.2 - Memory consumption 172 string-fasta 44 324 string-base64 152 164 math-spectral-norm 32 160 math-partial-sums 28 164 math-cordic 32 220 date-format-xparb 52 572 date-format-tofte 60 304 crypto-sha1 112 420 crypto-md5 152 268 crypto-aes 104 JerryScript 204 controlflow-recursive 136 Duktape 1.4 384 bitops-nsieve-bits 148 160 bitops-bitwise-and 24 160 bitops-bits-in-byte 24 160 bitops-3bit-bits-in-byte 24 172 access-nbody 36 160 access-fannkuch 32 240 access-binary-trees 76 216 3d-cube 76 0 100 200 300 400 500 600 700 Max RSS in KB (lower is better) Measured on a Raspberry Pi 2 Samsung Open Source Group 25 SunSpider 1.0.2 - Performance 6.46 string-fasta 3.21 5.95 string-base64 5.08 1.13 math-spectral-norm 1.46 3.73 math-partial-sums 1.57 3.62 math-cordic 2.83 2.23 date-format-xparb 0.83 4.64 date-format-tofte 2.09 1.93 crypto-sha1 2.07 2.08 crypto-md5 3.29 2.58 crypto-aes 3.36 JerryScript 1.51 controlflow-recursive 0.95 Duktape 1.4 4.52 bitops-nsieve-bits 17.88 10.75 bitops-bitwise-and 3.27 2.73 bitops-bits-in-byte 2.39 2.42 bitops-3bit-bits-in-byte 1.62 2.23 access-nbody 2.81 3.4 access-fannkuch 7.38 1.78 access-binary-trees 1.36 1.44 3d-cube 2.54 0 2 4 6 8 10 12 14 16 18 20 Execution time in seconds (lower is better) Measured on a Raspberry Pi 2 Samsung Open Source Group 26 ubench - Memory consumption 496 function-closure 32 156 function-correct-args 24 156 function-emtpy 24 156 function-excess-args 24 156 function-missing-args 24 JerryScript Duktape 1.4 156 function-sum 24 152 loop-empty 24 152 loop-empty-resolve 24 152 loop-sum 24 0 100 200 300 400 500 600 Max RSS in KB (lower is better) Measured on a Raspberry Pi 2 Samsung Open Source Group 27 ubench - Performance 18.87 function-closure 2.62 27.95 function-correct-args 22.18 38.89 function-emtpy 19.66 27.93 function-excess-args 20.85 27.35 function-missing-args 16.09 JerryScript Duktape 1.4 23.93 function-sum 18.05 55.23 loop-empty 30.14 6.41 loop-empty-resolve 3.42 76.65 loop-sum 35.48 0 10 20 30 40 50 60 70 80 90 Execution time in seconds (lower is better) Measured on a Raspberry Pi 2 Samsung Open Source Group 28 Demo Samsung Open Source Group 29 Tetris Demo ● Implementation of the classic Tetris game ● Each device drives one LED matrix as display ● Implemented as a Node.js module ● Both devices are running exactly the same JavaScript code Samsung Open Source Group 30 Demo LED Matrix LED Matrix I2C I2C Raspberry Pi 2 STM32F4 board (1GB RAM, 8GB Flash) (192KB RAM, 1MB Flash) Tetris Tetris Node.js IoT.js V8 JerryScript Linux NuttX USB Keypad Switches via GPIO Samsung Open Source Group 31 Tetris Demo https://youtu.be/q4iBeOAC7XI Samsung Open Source Group 32 Pong Demo ● Implementation of the classic Pong game ● Display shared across two devices ● Each device drives one LED matrix ● Implemented as a Node.js module ● "AI" oppenent running on the microcontroller Samsung Open Source Group 33 Demo LED Matrix LED Matrix I2C I2C Raspberry Pi 2 STM32F4 board (1GB RAM, 8GB Flash) (192KB RAM, 1MB Flash) Pong Client Pong Server Node.js IoT.js V8 Ethernet JerryScript Linux NuttX USB Keypad Samsung Open Source Group 34 Pong Demo Samsung Open Source Group 35 Future work Samsung Open Source Group 36 Future work ● Close performance gap between JerryScript and Duktape ● Further performance and memory optimizations ● Enhance JerryScript C API ● Add more IoT.js modules ● Package manager for IoT.js ● Support more devices Samsung Open Source Group 37 Summary Samsung Open Source Group 38 Summary ● Significantly lowers barrier of entry for JavaScript development targeting heavily constrained embedded devices ● Speeds up development ● Active community ● More information on http://www.jerryscript.net and http://www.iotjs.net ● Looking for bug reports and feedback Samsung Open Source Group 39 Thank you. Samsung Open Source Group 40 Contact Information: Tilmann Scheller [email protected] Samsung Open Source Group Samsung Research UK Samsung Open Source Group 41.
Load more

Recommended publications
  • Attachment A
    Board of Governors, State University System of Florida Request to Offer a New Degree Program (Please do not revise this proposal format without prior approval from Board staff) University of West Florida Fall 2018 University Submitting Proposal Proposed Implementation Term Hal Marcus College of Science and Engineering Computer Science Name of College(s) or School(s) Name of Department(s)/ Division(s) Bachelor of Science in Computer Computer Science Science Academic Specialty or Field Complete Name of Degree 11.0701 Proposed CIP Code The submission of this proposal constitutes a commitment by the university that, if the proposal is approved, the necessary financial resources and the criteria for establishing new programs have been met prior to the initiation of the program. Date Approved by the University Board of President Date Trustees Signature of Chair, Board of Date Provost and Senior Vice Date Trustees President Provide headcount (HC) and full-time equivalent (FTE) student estimates of majors for Years 1 through 5. HC and FTE estimates should be identical to those in Table 1 in Appendix A. Indicate the program costs for the first and the fifth years of implementation as shown in the appropriate columns in Table 2 in Appendix A. Calculate an Educational and General (E&G) cost per FTE for Years 1 and 5 (Total E&G divided by FTE). Projected Implementation Projected Program Costs Enrollment Timeframe (From Table 2) (From Table 1) E&G Contract E&G Auxiliary Total HC FTE Cost per & Grants Funds Funds Cost FTE Funds Year 1 150 96.87 3,241 313,960 0 0 313,960 Year 2 150 96.87 Year 3 160 103.33 Year 4 160 103.33 Year 5 170 109.79 3,426 376,087 0 0 376,087 1 Note: This outline and the questions pertaining to each section must be reproduced within the body of the proposal to ensure that all sections have been satisfactorily addressed.
    [Show full text]
  • Problems and Alternative Approaches Expanding the Scope of Software
    Expanding the Scope of Software Product Families: Problems and Alternative Approaches Jan Bosch VP, Head of Software and Application Technologies Laboratory Nokia Research Center Helsinki, Finland [email protected] © 2006 Nokia QoSA/CBSE 2006/ June 2006 Some background • Nokia Research Center since fall 2004 • Professor and Head of Software Engineering group at University of Groningen, The Netherlands - earlier head of RISE research group @ Blekinge Institute of Technology, Sweden. • Collaboration through research and consulting with, among others, Philips, Bosch, Thales, Baan, Avaya, Ericsson, etc. • Working IEEE/IFIP Conference on Software Architecture series, programme chair (2002), general chair (2004), steering committee member • Software Product Line Conference series • EU and ITEA projects, e.g. SeCSE (Service Centric Software Engineering) © 2006 Nokia QoSA/CBSE 2006/ June 2006 Overview • Introduction • Nokia and Nokia Research Center • Trends in Software • Platforms for Nokia Mobile Devices • Problems and Challenges • Alternative approaches • Conclusions © 2006 Nokia QoSA/CBSE 2006/ June 2006 R&D in Nokia • Global network with R&D centers in 11 countries • Over 20,882 people in R&D at the end of 2005 • R&D personnel represents 36% of Nokia’s total workforce • Nokia’s R&D expenditure totaled EUR 3,825 million in 2005 (11.2% of net sales) All figures are from Dec, 2005 © 2006 Nokia QoSA/CBSE 2006/ June 2006 Nokia Research Center – world-class expertise • Founded in 1986 • 1,097 employees at the end of 2005, or 5% of Nokia’s R&D
    [Show full text]
  • Pweb Peer-To-Peer Web Hosting Communication System and Dynamic Web Hosting
    pWeb Peer-to-Peer Web Hosting Communication System and Dynamic Web Hosting Alexander Pokluda1, Abdalla Aartail2, Md. Faizul Bari1, Reaz Ahmed1, and Raouf Boutaba1 1David R. Cheriton School of Computer Science University of Waterloo [apokluda | mfbari | r5ahmed | rboutaba]@uwaterloo.ca 2American University of Beirut [email protected] University of Waterloo Technical Report: CS-2013-15∗ ∗This report is a modified version of an internal technical report produced for Orange Labs, the project's sponsor. The original technical report was submitted to Orange Labs in August 2013. Abstract During the main phase of this project we identified and provided solution for the major challenges related to peer-to-peer (P2P) web hosting. More specifically, our solutions for naming, availability, ranking, indexing and dynamic web-hosting have been provided in previous reports. In this report we present a more concrete view of the pWeb infrastructure and address the issues related to a real-life deployment of the system. First we provide an overview of the light-weight P2P communication protocol between pWeb clients for signaling and media streaming in Part I. In Part II we provide an architectural overview of pWeb system and show the mapping of the abstract components in pWeb architec- ture to real life devices and technologies. In order to make pWeb compatible with the existing Web technology we have developed a DNS gateway. In Part II Section 3, we provide the design and implementation of this DNS gateway. For efficient indexing and fast discovery of end-user devices and multimedia content, we have developed a cloud-based solution for crawling, indexing and searching.
    [Show full text]
  • Final Report
    Team 4 - Rescue Drone Final Report Members Alexandra Borgesen [email protected] Peter Burchell [email protected] Cody Campbell [email protected] Shawn Cho [email protected] Sarah Hood [email protected] Halil Yonter [email protected] Sponsor Mr. David F. Merrick Faculty Advisor Dr. Rodney Roberts Instructor Dr. Jerris Hooker Reviewers Dr. Bruce Harvey Dr. Simon Foo 04/21/2017 Team 4 Final Report Rescue Drone Executive Summary UAVs used by Florida State University’s Emergency Management and Homeland Security Program can autonomously scan an area, but will provide no feedback regarding image contents, nor do they have a user-friendly interface for interprocess communication. The multidisciplinary ECE Senior Design Team #4 was tasked with creating a new, unique UAV capable of scanning disaster zones and identifying unique objects of interest. Careful research and planning has led to an innovative flight control architecture. The final product features a powerful onboard computer capable of live image processing for object detection, with distinct algorithms for color filtering and pedestrian tracking. A conversion algorithm was also implemented for converting the UAV’s latitude and longitude data, which is read from the flight control hardware, into USNG format. An IP network governs all communication between the ground station and the UAV. In the pursuit of increasing autonomy and implementing computer vision, a reliable and consistent object detection remains integral to accomplishing this task. By analyzing an image in search of HSV values that satisfy a predetermined range of color, any region of pixels that comply with the given range is highlighted using the color filtering algorithm.
    [Show full text]
  • Mobile Open Source Economic Analysis
    Mobile Open Source Economic Analysis LiMo Foundation White Paper August 2009 ™ ™ White Paper 1 Executive Summary It is possible to use quantitative techniques to examine a number of the proposed economic benefits of open source software. The claimed benefits are a reduction in cost of acquisition, access to innovation and cost of ownership of software technology. The quantitative techniques we use to conduct our analysis are based on measuring source lines of code (SLOC) applied to publicly accessible open source project repositories. To aid our analysis, we have developed a command line tool to mine information on open source projects using the ohloh1 web service. Based on this analysis, Based on this analysis, there is a strong case for constructive engagement with there is a strong case for open source communities where the corresponding open source software constructive engagement components are used within a collaboratively developed, open mobile software with open source platform such as the LiMo Platform™. communities... There is additionally a case for mobile software platform providers to consider using certain strategic open source projects as the basis for development of new functionality on their roadmap. There is no proven case within this analysis for converting existing proprietary items already within a mobile software platform to open source. To conduct a cost-benefit analysis of that scenario would require examination of more factors than SLOC alone. 1http://www.ohloh.net ™ White Paper 1 1. Introduction The subject of open source is increasingly important in relation to mobile device platforms and in view of this, it is vital to understand the underlying economic factors driving the use of open source software in a mobile context.
    [Show full text]
  • Symbian OS from Wikipedia, the Free Encyclopedia
    Try Beta Log in / create account article discussion edit this page history Symbian OS From Wikipedia, the free encyclopedia This article is about the historical Symbian OS. For the current, open source Symbian platform descended from Symbian OS and S60, see Symbian platform. navigation Main page This article has multiple issues. Please help improve the article or discuss these issues on the Contents talk page. Featured content It may be too technical for a general audience. Please help make it more accessible. Tagged since Current events December 2009. Random article It may require general cleanup to meet Wikipedia's quality standards. Tagged since December 2009. search Symbian OS is an operating system (OS) designed for mobile devices and smartphones, with Symbian OS associated libraries, user interface, frameworks and reference implementations of common tools, Go Search originally developed by Symbian Ltd. It was a descendant of Psion's EPOC and runs exclusively on interaction ARM processors, although an unreleased x86 port existed. About Wikipedia In 2008, the former Symbian Software Limited was acquired by Nokia and a new independent non- Community portal profit organisation called the Symbian Foundation was established. Symbian OS and its associated Recent changes user interfaces S60, UIQ and MOAP(S) were contributed by their owners to the foundation with the Company / Nokia/(Symbian Ltd.) Contact Wikipedia objective of creating the Symbian platform as a royalty-free, open source software. The platform has developer Donate to Wikipedia been designated as the successor to Symbian OS, following the official launch of the Symbian [1] Help Programmed C++ Foundation in April 2009.
    [Show full text]
  • January 2011 January 2011
    Editorial Chris McPhee and Michael Weiss IT Cost Optimization Through Open Source Software Mark VonFange and Dru Lavigne Best Practices in Multi-Vendor Open Source Communities Ian Skerrett How Firms Relate to Open Source Communities Michael Ayukawa, Mohammed Al-Sanabani, and Adefemi Debo-Omidokun Private-Collective Innovation: Let There Be Knowledge Ali Kousari and Chris Henselmans Control in Open Source Software Development Robert Poole Nokia's Hybrid Business Model for Qt John Schreuders, Arthur Low, Kenneth Esprit, and Nerva Joachim Recent Reports Upcoming Events Contribute january 2011 january 2011 Editorial 3 PUBLISHER Chris McPhee and Michael Weiss discuss the editorial theme: The Business of Open Source The Open Source Business Resource is a IT Cost Optimization Through Open Source Software 5 monthly publication of Mark VonFange and Dru Lavigne analyze the use of using free/libre the Talent First Network. open source software as a cost-effective means for the modern Archives are available at: enterprise to streamline its operations. http://www.osbr.ca Best Practices in Multi-Vendor Open Source Communities 11 EDITOR Ian Skerrett describes best practices for companies that wish to lower development costs and gain access to wider addressable markets Chris McPhee through engagement with open source communities. [email protected] How Firms Relate to Open Source Communities 15 ISSN Michael Ayukawa, Mohammed Al-Sanabani, and Adefemi Debo- Omidokun explore the relationship between firms and open source 1913-6102 communities. They illustrate the types of roles and strategies companies can employ to meet their business objectives. ADVISORY BOARD Private-Collective Innovation: Let There Be Knowledge 22 Chris Aniszczyk Ali Kousari and Chris Henselmans describe the benefits and risks of EclipseSource the private-collection innovation model, in which an innovator may Tony Bailetti chose to collaborate with others while still keeping some intellectual Carleton University property private.
    [Show full text]
  • International Journal for Scientific Research & Development
    IJSRD - International Journal for Scientific Research & Development| Vol. 2, Issue 11, 2015 | ISSN (online): 2321-0613 A Mobile Web Server Pradnya Gaikwad1 Priyanka Kumbhar2 Rupali Mahakal3 Pratibha Dekate4 Sandip Nagpure5 5Assistant Professor 1,2,3,4,5Department of Computer Engineering 1,2,3,4,5DCOER , Pune, India Abstract— In general the mobile device act as a client, employ firewalls that prevent access from the internet to because the conversion of IT and Mobile Computing phones inside that firewall. By implementing a custom domain the mobile device are also be viewed as a service gateway we could circumvent that limitation and we are hosting platform. Previously there is no any reason except now able to provide a web server on a mobile phone with a the storage area for the mobile device to act as server global URL than can be accessed from any browser, that because of less memory or less processing power, but due to means, the mobile phone has now finally become a full the Smartphone’s are introduce in market the problem is no member of the internet. more. Now a day the mobile devices have that much storage There are many software technologies related to the space. We are proposing a mobile web server which is mobile web server field. software that provides a mobile device such as a smart A. Nokia S60 Web Server: phone or tablet, the capability, to host web sites, web application, and web services. In this paper we are Nokia one of the few cellphone companies brought Apache proposing a web server which can run on a mobile device HTTP Server to their line of Nokia cellphones, running such as a Smartphone.
    [Show full text]
  • Mobile Web 2.0 Developing and Delivering Services to Mobile Devices Edited by Syed A
    Telecommunications / Digital & Wireless Communications Ahson Ilyas Mobile Web 2.0 Developing and Delivering Services to Mobile Devices Edited by Syed A. Ahson • Mohammad Ilyas Mobile Web Web Mobile From basic concepts to research grade material, Mobile Web 2.0: Developing and Delivering Services to Mobile Devices provides complete and up-to-date coverage of the range of technical topics related to Mobile Web 2.0. It brings together the work of 51 pioneering experts from around the world who identify the major challenges in Mobile Web 2.0 applications and provide authoritative insight into many of their own innovations and advances in the field. To help you address contemporary challenges, the text details a conceptual framework that provides modeling facilities for context-aware, multi-channel Web applications. It compares various platforms for developing mobile services—from the developer and user perspectives—and explains how to use high-level modeling constructs to drive the application development process through automatic code generation. • Proposes an expanded model of mobile application context • Explores mobile social software as an Information and Communications Technology (ICT) • Discusses the effect of context on mobile usability Through empirical study, the book tests a number of hypotheses on the use of software implementation technology and location context in mobile applications. 2.0 It introduces Reusable End-User Customization (REUC)—a technique that allows users to adapt the layout of Web pages and automatically reapplies those preferences on subsequent visits. It also investigates the need for non-visual feedback with long system response times, particularly when downloading Web pages to mobile devices.
    [Show full text]
  • Mobile Personal Website
    Mobile Personal Website Johan Wikman∗ Ferenc D´osaR´acz† Nokia Research Center Nokia Research Center 1 INTRODUCTION *.raccoon.net ⇒ Gateway IP Address Thus, when someone browses to, for instance, Most, if not all, smartphones of today are, in terms of processing http://john.doe.raccoon.net and the browser does a power and the amount of available memory, on the same level as or domain name lookup it will resolve to the IP address of our gate- even surpassing the servers of the early web. In the beginning of way. However, when the browser subsequently opens a connection 2004 we started a project at Nokia Research Center with the aim of to the gateway and submits the request, the header will still contain exploring what implications it would have if it were possible to host the original host name http://john.doe.raccoon.net. a website on a mobile phone and if that website were addressable in and accessible from the Internet, using the operator networks of today. mobile gateway web 2 WEB SERVER terminal browser HTTP We set out with the intention of putting a full-fledged web server, Conceptual HTTP traffic daemon that implements the full HTTP protocol, on a mobile phone. Due HTTP reverse TCP to the modest size of the project, creating a web server from scratch port HTTP proxy HTTP socket local was not a realistic alternative and instead we chose to port Apache internal port httpd[2]. call Apache is implemented on top of APR[4] — Apache Portable proprietary Runtime — which is a software library whose intention is to provide mobile protocol gateway connector connector a predictable and consistent interface to an underlying platform- TCP specific implementation.
    [Show full text]
  • MMM Mobile Web Server Experiment Report
    MMM Mobile Web Server Experiment Report Created by Antoine RJ Wright for Mobile Ministry Magazine Edited by Kevin Agot and Antoine RJ Wright Last Revised: June 7, 2008 Table of Contents Summary Part 1 • Reasons and Goals of the Experiment • Explanation of Nokia's Mobile Web Server and my Device • Social Networking Component Part 2 • Day-to-Day Usage • Immediate Challenges • "Accessibility" versus "Versatility" Part 3 • Lessons Learned • Current and Future Applications • Why This Is A Model for the [Digital] Church Appendix Summary It was not that long ago that the faster desktop computers were running at 400MHz, had 8GB hard drives, and could connect to a plethora of networks. It was a pioneering time for the personal computer, and forwarded the use of Internet and collaborative technologies like no other media had done before it. But as things got faster, they also became smaller. Desktops turned into laptops; laptops turned into smartphones and tablet PCs. The ability for personal computing to take on a personal focus because easier as these devices became smaller and therefore easier to assume into our lives. Nokia's Mobile Web Server signals the sign of yet another aspect of computing being made smaller and more accessible - the web server. The web server acts as the island by which websites are served and users congregate with one another. By taking the physical location of the web server to the mobile device, Nokia opens the door for more accessible and versatile uses of websites than has been done before. At the same time, the introduction of such software also signals that not everything is ready to be put into our hands yet.
    [Show full text]
  • Full Range of the Core Applications of the Phone Over the Web Using a Regular Web Browser
    INTERNATIONAL JOURNAL OF RESEARCH IN COMPUTER APPLICATIONS AND ROBOTICS Vol.6 Issue 7, Pg.: 1-3 July 2018 www.ijrcar.com INTERNATIONAL JOURNAL OF RESEARCH IN COMPUTER APPLICATIONS AND ROBOTICS ISSN 2320-7345 MOBILE WEB APPLICATION DEVELOPMENT Vinod Kumar Mishra Ranveer Rananjay Post Graduate RRPG College, Amethi, Uttar Pradesh India Abstract -We will demonstrate how a common mainstream web application development stack, the so-called AMP stack, can be installed on a mobile phone and used for creating a mobile website that utilize the unique characteristics of a mobile personal device. By providing a widely used web application development environment also on the mobile phone, we foresee that the threshold for developing mobile websites effectively can be removed. I. INTRODUCTION All high-end mobile phones of today are equipped with web browsers that allow users to browse the web. In general, mobile phones — in particular so-called smartphones — are increasingly becoming like general purpose computers and functionality that traditionally have been available only on regular computers is being migrated to them. However, so far mobile phones have not really been used as servers – in particular, web servers – although they in terms of processing power and the amount of available memory are on the same level as, or even surpassing, the servers that were used when the web was in its infancy in the early nineties. In the beginning of 2004 we started a project at Nokia Research Center with the aim of exploring what implications it would have if it were possible to host a website on a mobile phone and if that website were addressable in and accessible from the Internet, using the operator networks of today.
    [Show full text]